I have the field, "Epic Link", as a field on Screen_A. Screen_A belongs to Issuetype_A. Screen_A belongs to field configuration_A. I use the "where is my field" functionality in JIRA, and it suggests that the field should be on the form.
But, it is not on the form. I re-index the data via JIRA. Still not there.
JIRA shows in the field configuration that this field is locked and that it is used by Greenhopper, yada, yada. That makes sense.
But. my problem: I have several issues that have been closed, but I want to associate them with the Epic to get a true picture of value produced and destination it has taken to get there, yada yada. But, I can't because a) the issue is closed and no longer present on the GH side to make the association, and b) I can't present the field on the form to make the association. And yes, I'm speaking about the latest Epic functionality from Greenhopper, not some legacy implementation of basic issue links that we once used.
Figured I'd ask my friends before seeking support from Atlassian.
Unfortunately, there's no possible way to edit the epic link from the issue itself. You may want to vote on the following 2 tickets:
To associate some old issues to the Epic, you may want to try the approach from Michael, which use additional board and filter to achieve it:
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs