Hello,

Thank you for submitting your feedback.

We have successfully addressed the bug you reported. Moving forward, you will be able to link issues to epics in projects you can view but can't edit. Previously, you needed permission to edit both the issue and the epic.

Hi 06e1a05bfb3d, sorry the previous comment was responding to an internal comment that was not what this ticket was discussing, so back on the original problem raised, the epic link field is deprecated and replaced with parent field https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/ and the described situation would display a clear error message as below

 35e487d58ea2 this is a problem when a user is working in the issue to be joined to the epic. So if I am a user working on a story that i have permission to edit, and I add an epic that I do not have permission to edit to the parent field, it fails silently with no error.

Hi Ahmud, 
Are you still looking for input? The use case is straight forward: 

For teams that collaborate cross-team (and cross-Jira-project) need to be able to link issues (from team A) to Epics from other teams (team B). But teams (B) don't necesarily want these 'contributing teams' (Team A) to be able to Edit these Epics (or other issues in the project of team B). 

Many large organisations will have this requirement. 

Let me know if you need more info. Or if you have an update on planning and timelines of resolving this issue: please also post an update. 

Thanks. Have a nice day! Rik

Hello,

I am a Product Manager on the Jira Issue View team. 
Thank you for taking the time to share your valuable feedback with us.

Your input is greatly appreciated, and I would like to learn more about your specific use case to better understand this bug. Could you please book some time with me using this Calendly link? Alternatively, feel free to reach out to me at aauleear@atlassian.com if you prefer.

Thank you again, 

Ahmud 
PM-Jira Cloud

The bug has been reopened once again. 

The side effects of the fix have caused disturbance to Jira customers in different experiences. Having in mind the good of the customers, the team has decided to roll back this fix and prepare an alternative solution in the upcoming weeks.

We'll update the ticket once the decision on the next steps is made. 

Hi gmountakis,

I've built a custom validator to avoid this problem so far. Since the fix now validates before validators come into play, my users get your error message instead. The problem is: The new error message does not indicate what the problem is. Instead, it just says "Couldn't create the issue. We're having some trouble creating the issue. Refresh the page and try again." - of course refreshing the page doesn't help the permission issue of the reporter.

Do you plan on changing the message in the future or can I somehow opt out of this solution?

The bug fix should now be deployed to all users, don't hesitate to leave a comment if you're still seeing the problem, thanks!

I am encountering this issue in a Next-Gen project.

I am configuring a "structured" project, and as part of this, want to prevent users from editing issues by clicking directly in fields, forcing them to use transitions which have been created with custom screens to control the fields that can be changed at different parts of an issue's lifecycle. I am encountering this bug. This is affecting my entire company.

To reproduce this issue:

• Create a project
• Create a screen with a single field added to it: Epic Link
• Create a copy of the default workflow. Add a new transition from "Open" to "Open", called "Link Epic". Add the screen made in the previous step to this transition
• Create a copy of the default permission scheme. Remove the "Any logged in user" permission grant from the "Edit Issues" permission
• Associate the new permission scheme with the project
• Use the global "Create" button to create an Epic in the project
• Use the global "Create" button to create a Story in the project.
• View the detail page for the Story you just created
• Click the button for the "Link Epic" transition in order to open the screen modal
• Add the previously created Epic as the Epic Link
• Click the blue "Link Epic" confirmation button
• Watch the issue detail view reload, and notice that there is no Epic Link
• View the detail page for the Epic you created earlier
• Notice that there are no Child Issues
• Click the "Create issue in epic" button. Enter a title for the issue and press Enter.
• Notice that the issue displays in the "Child Issues" section on the Epic's detail page
• Refresh the page. Notice that the issue is no longer displayed there, and has no association with the Epic whatsoever

As noted in this issue's description, this issue also occurs when adding the Epic Link in the Create Issue screen.

This bug has been open since 2016.  What is the likelihood it will actually be fixed?  This is impacting my entire IT org.