The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips

E-mail notifications are sent ahead of the blog post's approval.

Currently, if a user subscribed to notifications for all blog posts, the e-mails are being sent the moment a blog post is created. Normally they should be sent only after a blog post has been approved (provided that an approval workflow is being used).

Notifications are sent before a post is published.

If a blog post is scheduled, under certain conditions notifications will be sent before the scheduled time has arrived. This behavior occurs, if a user has watched all blogs or is following the creator and in addition has writing permissions to the news space.

Brikit Theme - loss of metadata

When Linchpin Enterprise News is used in combination with Brikit Theme, saving a blog post results in lost metadata (teaser settings, publish time etc.) of the blog post.

NoEmailStorm - missing buttons

When Linchpin Enterprise News is used in combination with NoEmailStorm, NoEmailStorm buttons won't be displayed while editing blog posts.

The blog post preview is broken for anonymous users.

Currently, the blog post preview doesn't display all elements for anonymous users.

Blog posts created via API do not enter approval workflow.

If a blog post is created via an API, e.g. by a third party app, in a workflow space, it is published immediately and does not enter the approval workflow. Blog post can only enter the approval workflow, if they are created with the editor.

Confluence's notification mail displays the last person who made changes to a blog post as its author.

If person A creates a blog post and submits it for approval, and person B fixes a typo (or changes anything else in the blog post) and then approves it, the mail that is sent out from Confluence displays person B as the author.

User mentions provide access to information ahead of the blog post's approval.

Currently, when a user is mentioned in a blog posts, they receive a mention immediately. This will happen even if the blog post has not been approved yet (provided that an approval workflow is being used). This way, the mention could leak information to this specific users. 

When copying or moving published blog posts into other spaces, they enter the approval workflow for the target space again.

Otherwise, an enabled workflow could just be circumvented by creating/publishing news in another space and then moving it to a space reserved for important information. All news items are "published" only in the context of their respective space, and this status resets whenever moved into a space with enabled workflow.

The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips

Confluence-wide file upload may be broken when Linchpin Events is installed.

There currently is an issue that prevents users from uploading some files to Confluence pages when Linchpin Events is installed in that instance.

Calendar invitations

The ICS format, which Linchpin Events uses to generate calendar invitations, can in some cases behave unexpectedly. This usually depends on the calendar clients being used to import the invitations. If you run into any problems in this area, please reach out to our support team at https://seibert.biz/help and also check whether the issue persists in other calendar software!
Right now, we are aware of the following incompatibility:

Lotus Notes Calendar: All-day events spanning across several days are only imported for the start day.

Linchpin Events overrides Space Privacy settings.

When an event is visible to all users (and not restricted to specific spaces), all users will be able to see the event, even if Space Privacy settings would forbid this. This can happen e.g. for events that were created while Space Privacy was not active.

The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips

Many error messages occur when a user has not accept the Terms of Use yet. 

If a user logs in into Linchpin Mobile without accepting the system's Terms of Use, many error messages will be displayed.

Android: The date and time of an event is displayed incorrectly when the text takes up two lines. 

When viewing an event in Linchpin Mobile, the time and date of an event might be displayed incorrectly if the text reaches a second text line. The text in the second line will then be cut off.

Android: Push notifications icon is not displayed correctly. 

Currently, the push notifications icon might be displayed incorrectly on some Android devices. Currently we know that Android version 7 & 8.1 might be affected.

The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips

Many error messages occur when a user has not accept the Terms of Use yet. 

If a user logs in into Linchpin Mobile without accepting the system's Terms of Use, many error messages will be displayed.

Android: The date and time of an event is displayed incorrectly when the text takes up two lines. 

When viewing an event in Linchpin Mobile, the time and date of an event might be displayed incorrectly if the text reaches a second text line. The text in the second line will then be cut off.

Android: Push notifications icon is not displayed correctly. 

Currently, the push notifications icon might be displayed incorrectly on some Android devices. Currently we know that Android version 7 & 8.1 might be affected.

Android: PIN is requested too often.

Currently, on Android devices, if you set up a PIN for your app, Linchpin Mobile will ask you to enter the PIN in various situations, like when giving feedback or taking a picture to insert it into the Microblog. We know that it happens too often and we try to think of a good solution.

Some CMYK images might not be displayed.

When an image of the CMYK color model is uploaded to your Confluence instance, Linchpin Mobile might have troubles opening said image and might display an error message.

If a user didn't accept the Terms of Use yet, Linchpin Mobile won't automatically generate content on login.

This bug relates to the other Terms of Use bug. If a user logs in into Linchpin Mobile without having accepted the Terms of Use, the content (for example the news) won't load automatically. The user has to refresh the page by themselves for the content to load.

Android: Connection issues to system which use mobile device management (MDM).

If your Linchpin system lies behind a firewall/VPN of a MDM, connection errors might occur. We are actively working on sorting this issue out and improve the connection between Linchpin and MDMs.

Swipe gestures make it possible to re-enter the onboarding module.

After a user initially started Linchpin Mobile and completed the onboarding regarding push notifications and analytics, they can return to this screen if they use a swipe gesture for "back". This is not intended.

Android: Sometimes, the text placeholder for the first PIN request doesn't work.

When you initially start Linchpin Mobile and have activated the PIN feature, the text placeholder (for example: Please enter your PIN code) isn't displayed correctly. Instead, the i18n-key is shown (for example: security.pin.dialog.title).

Using gestures to navigate through the app might lead to buggy animations.

When a user uses a swipe back gesture, for example to leave a menu, and it happens very quickly after some element has been loaded, the animations and the reload of the content might have some bugs.

User search might display an error message although it works correctly.

Sometimes, the user search might display an error message that the search failed. It is not the case and after some time, all relevant search results will be displayed. We are investigating this issue.

General issue

The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips

Theme reset to Confluence default after upgrade of Linchpin apps.

Updating Linchpin Theme disables the theme for a brief period. If the Confluence system is accessed by another user during this time, it detects a "missing" theme and resets Confluence to the default theme. 

Solution: To repair this, simply activate the theme again. Starting with Confluence 6.15 this is not an issue anymore, so we suggest updating.

Sidebar icons break when a system is migrated from HTTP to HTTPS.

If you migrate your system from HTTP to HTTPS, the sidebar might display broken icons.

The issue exists because the sidebar uses the base URL of the system to load faster. Sadly, the sidebar does not flush the cache automatically, that's why you have to do it yourself after performing a migration.

Workaround: To fix this issue, please navigate to Confluence administration → Cache management.

Look for the net.seibertmedia.confluence.linchpin-sidebar.cache.sidebar.v2 key and click on the Flush button.

Settings for not showing the menu in space themes get reset.

When using space themes with deactivated menu and upgrading to Linchpin Theme 2.19.x or Linchpin Suite 2.x, the settings for the menu get reset to default. That means that the spaces using those space themes will show the menu.

Workaround: The setting has to be corrected once after the upgrade, from then on they keep their settings.

Teaser images are missing in PDF exports.

Teaser images are missing when a page is exported to a PDF.

A time-out leads to lost changes in menu configuration.

Changes in the menu configuration can disappear when the admin times-out.

A 1/3 page layout makes the Spaces macro disappear.

The Spaces macro can disappear when displayed in a 1/3 page layout.

Pop-ups are displayed in wrong positions.

The login page sometimes can cause pop-ups to appear in wrong positions. This is fixed with Linchpin Theme 2.20.4.

Text inside the header might appear cut-off.

Text inside the action drawer (header) can appear cut-off when it's displayed in two rows.

The placeholder text inside the search bar might appear cut-off.

The placeholder text inside the search bar (for example: "Type to use the search") can appear cut-off.

The following apps and versions are known to have compatibility issues with the Linchpin Theme. These might have been addressed by a more recent release of the third party apps.

• Announcement Banner for Confluence 1.9.2

The 'My Contacts' macro isn't being displayed in PDF exports.

Currently, the 'My Contacts' macro isn't being displayed when you export a page to a PDF file.

Links which contain single quotation marks do not work properly.

Inside the configuration of LUP, some links may be broken if they contain the single quotation mark (').

Copying content and the 'Content Responsibility' macro

The 'Content Responsibility' macro maintains its own data structure separate from Confluence content (pages, blog posts or dashboards). As a result, when you copy content including the macro (manually or through third-party apps like bitvoodoo's Templates for Blog Posts for Confluence), the resulting pages will require you to fill out the responsible user(s) again and save/update the content. The macro settings will carry over.

Embedding the 'Content Responsibility' macro in blueprints is supported, but the created pages will also need to be saved/updated once for the data to be handled correctly.

Sometimes the profile editor displays Skype configuration options for the XMPP instant messenger field type.

If a Skype IM field was created first, and then a XMPP IM field is created, the profile editor will still display the configuration for Skype instead the one for XMPP.

The 'Customized User List' macro displays horizontal lines double. 

The horizontal lines separating profile fields are displayed double inside the macro.

If a second Skype for Business instant messenger fields is configured to show the online status, a wrong message appears.

If a second Skype for Business instant messenger field is inserted into a profile and it's configured to show the online status, a message asking to replace profile field data will be displayed (this should not be the case).

The "Atlassian Troubleshooting and Support Tools" app in version 1.32.1 causes problems for the Linchpin Intranet Suite.

For more information, follow the link below:

Knowledge Base: "Atlassian Troubleshooting and Support Tools" app causes health checks to freeze and blocks the creation of support zips

Attachments can't be edited. 

In version 5.0.x, it's not possible to edit attachments. 

MultiExcerpt by Artemis Software

The Microblog is not compatible with the MultiExcerpt app by Artemis Software in versions 5.2.16 and above.

The MultiExcerpt app causes the Microblog to freeze the page, when entering mentions, quotes or links, adding a new line, pasting images and other cases.

Workaround: We suggest downgrading to Version 5.2.15 or uninstalling the MultiExcerpt app.

Attachments are deleted from the server even without saving the changes.

When attachments are deleted during an edit, but the changes are not saved, the attachments will still be deleted from the server (and the preview links won't work).

Blog posts which use the Microblog macro can't be deleted.

Currently, the blog posts which use the Microblog macro can't be deleted.

Rare bug prevents the usage of links inside the editor.

In isolated cases, problems with links might occur. A very rare bug can occur where it's not possible to input the link address and thus it's not possible to create hyperlinks inside the editor.

SVG files may not be displayed correctly in the Microblog.

Currently, due to the differences in image sizes, SVG files might not be displayed properly in the Microblog.

Two buttons, one icon - "Select all" and "Deselect all" buttons use the same icon.

The "Select all" and "Deselect all" buttons inside the Microblog portal currently have the same icon.

Very long space and topic names can lead to text overlaps.

A visual error may occur with topic and space names. Very long space and topic names can lead to text overlaps.