Updated 3rd Dec: Changes to the linked issue creation experience in JSM

[#1]

Update, 3rd December 2024:

We have decided not to go ahead with the change below. We have found a way to continue supporting attachments when creating a linked issue from the issue view.

There will be no changes rolling out to JSM.

Thanks,

Sam Knight

---

Hello community,

Starting in December, you can no longer upload an attachment when creating a linked issue from the issue view in Jira Service Management. We’re doing this to ensure Jira Service Management is FedRAMP compliant by migrating from a weaker encryption/decryption method (SHA1) for uploading attachments to a stronger one (SHA256).

There are a two workarounds that can be used:

Option 1 - attach after issue is created

1. Open an issue in the issue view and select ‘Link issue’

2. Then, under the ‘Linked issues’ section, select ‘Create linked issue’

3. Continue creating a linked issue as usual

4. Open the linked issue created in the issue view, expand the description field, and then select ‘Add, image, video, or file’ to upload an attachment

Option 2 - use Global Issue Create

1. Select ‘Create’ to open the Create screen

2. Then link it to an existing issue, continue to enter field values, and upload an attachment as per usual

   • If you prefer to use field values from an existing issue, open the issue in the issue view, resize the screen to the dock, and then copy-paste select field values from the source issue

3. Create the linked issue

We are aware of the impact of these changes on your workflow and efficiency and apologise for any inconvenience. Additionally, if you’d like the feature to use the modern issue create experience, please vote and add your comments on JSDCLOUD-3917.

Thanks,

Sam Knight

Principal Product Manager, Jira Service Management

[John Funk]

Awesome changes - thanks @Sam Knight !!

[Metin Savignano]

SHA1/256 is not an encryption algorithm, and I don’t understand how the algorithm could affect when the upload of a file is possible or not? 

[Rick Westbrock]

I too do not understand how an encryption algorithm change would impact uploading a file during linked issue creation differently than global issue creation. As a developer myself I'm very curious about what the technical constraints are for this.

[Sam Knight]

Hi all - forwarding on the below message to go deeper into the reasoning behind the change.

Thanks,

Sam

SHA-1 (Secure Hash Algorithm 1) and SHA-256 (Secure Hash Algorithm 256-bit) are cryptographic hash functions which are used to ensure data integrity,  file verification etc.

How these algorithms can affect upload attachment?

1. Integrity of attachments being uploaded by users(Ensuring the file integrity).
2. Deduplication: Prevent storing multiple copies of the same file.

Why the attachment functionality has to be deprecated?

Since legacy experiences uses SHA-1 & given the vulnerabilities in SHA-1, using it for hashing the files/attachments is not recommended hence Atlassian is moving to SHA-256 which is a stronger hashing algorithm and this is only available on Modern experiences such as modern CLI.

[Sam Knight]

Update, 3rd December 2024:

We have decided not to go ahead with the change. We have found a way to continue supporting attachments when creating a linked issue from the issue view.

There will be no changes rolling out to JSM.

Thanks,

Sam Knight

[John Funk]

Hooray!!