Here Initiative Epic Feature Story Task is the Hierarchy want to achieve.
Portfolio take care of Initiative-Epic
The problem comes with Epic-Feature-Story, how to achieve?
With Structure plugin, I linked Epic Feature and Story but the problem is when I update story tickets there's no progress in Epic in the Agile Backlog Board, epic progress gets updated only when the feature is updated there's no relation between stories and epics now.
I don't think we can rename default Epic Issue Type and change it to Feature?
You can actually change the name of the Field that will work as an Epic on Agile boards to anything you want, including Feature.
The parameter that makes JIRA treat the type as Agile Epic is Description, which says: gh.issue.epic.desc
Here is an example of such setup:
As for rollin-up progress, you should be able to see it in Structure. If something doesn't work, please let us know and we'll be happy to look into it. You can leave a comment here or open a ticket in our JIRA:
Eugene (ALM Works)
Hi Dave, Deni,
A quick update on the Strucutre side - we've added support for Portfolio Parent links so you can now use two tools together (most customers would use Porfolio for planning and Strucutre to tracking and other everyday activities).
Here is a series of blog posts covering this use case. Maybe it will be useful for you:
Eugene (ALM Works)
I'm not sure what could be the case there. Maybe something was changed in the later versions of Jira.
What might be worth checking is this addon:
I haven't tried it myself yet, but it seems like a good far more complete solution for this scenario - it even translates the link type name and works for JQL queries too.
I hope this helps.
What? Jira is unable to create the following hierarchy out of the box?
So how do you view details for tracking purposes. This is all out of the box functionality in Team Foundation Server.
If Jira does not allow this or does not understand that this is basic Agile/Scrum software development then its not fit for purpose.
Thanks for your post.
If you could share a bit more information about your specific hierarchy (Issue Types used, how many levels etc...), I'd be more than happy to make some recommendations.
But as an example, you could take advantage of Structure's Automation Feature to bring your Epics into a structure, using the Insert Generator. Once you do that, you could use the Extend Generator to visualize Stories under Epics, Linked Issues under Stories, and Sub-Tasks as needed. You could even Group your Issues by Sprint after that.
I wanted to briefly mention how Structure could help you visualize your Jira issues but I'll be more than happy to address your particular case in more detail if you'd like. I can be reached at firstname.lastname@example.org and our Support Team is always eager to help at email@example.com.
I look forward to hearing back from you.
Simply repeat step 3 to show Tasks and Bugs under Stories by choosing the appropriate Link Types.
Note: Please always make sure you're focusing on the top level of your structure (the row with your structure's name will be highlighted in blue) to ensure that the Generators are being properly applied to the whole structure.
I hope this helps. Please let me know if you need further assistance. Our Support Team can also be reached through our Service Desk portal by emailing firstname.lastname@example.org.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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