Using the associate issue to epic link doesn't work in current GH version

We've updated to the latest GH version and clicked on the + next to the Issues in Epic link to create a new issue. However, doing so, creates an issue, but doesn't actually associate it to the epic.

Any ideas?

2 answers

1 accepted

0 votes
Accepted answer

With the latest GH upgrade, this issue has been resolved.

0 votes
Jay Rogers Atlassian Team Mar 04, 2013

G'day Mate.

If you go to the Epic in JIRA (click the issue key in the expanded Epic details) and look at the View Issue page, does your issue appear in the "Issues in Epic" block? It may be that some aspect of your board filter is preventing the new issue from appearing on your board...


It does; but,

1) you have to create a scrum board to do this. Our scrum boards don't have items in the backlog that have not been groomed. We use kanban boards for the process of vetting out issues to get them ready for grooming and then groomed. Epics are not supported in kanbans.

2) The section doesn't appear until you have at least one issue already associated with an epic.

We were looking for something that was consistent with how JIRA issues work. Under More Actions, we expected to then see add to epic or something like that which is similar to links or attachments that allow users to associate items. Or, be able to use one of the fields like Epic Link on edit/create. You can add these fields to a screen, but they never appear.

Right now, the feature is just way too restrictive and process controlling vs providing a feature that aligns with how JIRA works and be supported across any GH board, and allowing customers to incorporate into the process. Its too intrusive force customers to change their processes to accommodate GH; especially when its inefficient. Atlassian should focus on functionality and not limit it to only scrum processes and force a process. You can provide best practices guide, but you are losing adoption and a large market that uses GH for something other than scrum development; majority of our boards are kanban because we use it for product grooming, measure releases that are tied to CMS programs because you release measures and protocols as they are configured, there is not a specific release cycle, but measures and protocols fall under speciifc programs or initiative, which are epics; we use them for client implementations and specific company projects and initiatives, and several others. All of which have epics as an epic could be a phase, initiative, campaign, etc.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

131 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you