Hi,
the following problem: I have created an Epic. Then I create a task and want to assign it to the Epic. I can do this either directly when creating the task or later in the detail view of the task. Both works.
However, when I close the task and open it again, the Epic link is not displayed in the task detail view (more precisely: it appears for a fraction of a second when the page is loaded and then the "Epic link" field is empty). When I open the Epic, the assigned task is displayed correctly.
I.e. the assignment has worked but in the task detail view it is no longer visible. What could be the cause of this problem? Can someone give me a hint?
best regards
Thomas
Was there any answer to this? I'm having the exact same problem. It shows the Epic link being set in the issue activity and the Epic link field appears populated. Likewise, after reloading my Epic link is blank. However I do not see the Task listed under Issues in the Epic as Thomas did.
Update: I was a project admin in the Jira project of the issue I was editing. But I had no project-level permissions in the project that the Epic that I was linking to was in. After making myself an admin of the Epic's project, I was then able to set the Epic link on the issue and have it stay.
I guess it makes sense that I shouldn't be able to add tasks to an Epic in a project I have no access to... It's just strange that it would allow me to edit the Epic link, then silently remove it due to a permission issue, rather than not allow me to make the change at all and/or provide me with an error message.
Hi,
The behavior here sounds like something is changing the value for that field. Perhaps automation. Try looking at the issue History. I think in your screenshot it would be the button that's called 'Verlauf' within the issue view.
This can at least show you the value of that field historically. As well as who might have changed it.
Alternatively, in the issue view, there is the Automation field, you can click the Rule Executions, which will change that view to show you the most recent automation rules that have executed on that particular issue. If you have an automation rule changing field values on the issue, then this is the most likely explanation for the behavior presented here.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Note that the user said even though the Epic Link field is blank in the child issue, when viewing the Epic itself the issue appears there as a child of the Epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
in the history there is only the entry, that I assigned the ticket to the epic. For better explentation I've created a new ticket. As you can see in the history there are only 3 entries, see below.
The automation does not deal with the epic field.
Regards,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas,
Thanks for that information. I created a support case on your behalf over in https://getsupport.atlassian.com/servicedesk/customer/portal/23/JST-796818
Please grant our support team access to your site. With that, our team can investigate the behavior here in more depth.
Cheers,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Thomas - Welcome to the Atlassian Community!
Can you share some screenshots?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John,
here are a some screeshots:
1. picture: I assigned the epic link "Epic #1" to the ticket.
2. picture: After reload the page the entry of epic link disappeared.
3. picture: When you look into the Epic, the ticket is assigned.
kind regards
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay, thanks for sharing all of that. Since you are on a Free subscription, let me see if we can get someone from Atlassian to take a look at it for you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.