Advanced Roadmaps for Jira Software Standard

[atarab]

Hi,

We have Jira Software Standard. 

Is there a way for us to get Advanced Roadmaps as an add-on, without needing to switch our entire instance to Jira Software Pro?

Thank you

[John Funk · Accepted solution]

Hi @atarab  - No, you must have a Premium subscription in order to get Advanced Roadmaps. 

[Ravi Sagar _Sparxsys_ · Accepted solution]

Hi @atarab 

As @John Funk mentioned you need to have premium, do you have the list of requirements related to road maps? I guess the in built roadmap is not sufficient for your requirements. There are other apps like Structure, BigPicture that might be helpful.

Do take a look at these apps from the marketplace.

Ravi

[atarab]

Thanks, @Ravi Sagar _Sparxsys_ and @John Funk

Our main requirement is a more flexible hierarchy. More specifically, we would need a level between Epic and User-story, so the hierarchy would be:

Epic -> Feature -> User Story -> Subtask. 

I've been experimenting with the structure add-on, but I found that while it allows me to display User Stories as children of features (based on a custom issue link I created called "Implements/Implemented by"), it is only a display, not a real parent-child relationship.

This creates two problems:

1. It is less convenient, because Stories cannot be created from inside a feature (the way they can be created in Epics, or the way Subtasks can be created in stories), but need to be created independently and then linked. This is not a big problem, but it is definitely inconvenient for our teams. 
2. This is the bigger problem - we use a different program called Craft.io to plan our big picture, and to write our Epics, releases etc. This program integrates with Jira but does not allow up to map our tickets there to the hierarchy we want in Jira, because they don't recognize Feature -> User Story as a parent-child relationship. 

 I saw somewhere that using Advanced Roadmaps you can create a more complex hierarchy for real, not just as a display. 

Is this true?

Thank you,

Atara

[Andreas Haaken (APTIS)]

Hi @atarab , 

we have implemented Container Links on Server/DC in Epic Sum Up, that gives you the ability to create these hierarchies:

We are working on this feature for cloud, too. Would you be open to let us know what the requirements are that you may use that feature? I am talking about the parent-child connection... (on Server we use a field, on cloud this is more complicated)

[atarab]

Hi @Andreas Haaken (APTIS) ,

First, allow me to compliment you and say the add-on looks excellent. 

My issue with it would be that the containers are only there to give a visual view, but are not an issue type, and therefore don't have fields of their own. 

They cannot be assigned or commented on. They cannot have a label, or any other system, or custom Jira field. 

They also cannot be mapped into automatically by the integration to the external app we use, since they are not an issue-type and therefore will not be recognized. 

[Andreas Haaken (APTIS)]

Hi @atarab , 

Oh, the Containers are Issuetypes, thats exactly the reason why we added container functionality to any issuetype you define. 
You can see that in the image, that the containers have values as all other issues, in the view they summarize them if collapsed. In expanded view you see that they have their own values. Example: Time Budget on the Release Issue, see this:

On the Server/DC Side we have an API that allows you to find these Container Issues and request their summaries. I am not sure if this will be possible on Cloud, too. But Thats why we are looking for requirements. :) 
But: On the cloud the containers will also be issues, that already in development :)

[atarab]

@Andreas Haaken (APTIS) ,

Oh, very nice. 

How is the relationship between a container and a child defined?

And when will the cloud version be available? 

[Andreas Haaken (APTIS)]

@atarab 

On the Server/DC the connection is stored in a custom field called "Container Link", so its the same as Epic Link or parent (used by Atlassian). 

In the cloud there are some restrictions about data and Custom Fields. We are waiting for Forge to solve that or build it based on properties in the mean time. 

Release is planned early 2022

[Dave Rosenlund _Trundl_]

Hi, @atarab. All parent/child relationships in Jira are defined by issue links - whether they are out-of-the-box Jira issue links or custom issue links you create.

That said, those out-of-the-box Jira (and/or <Advanced> Roadmaps) issue links have some special built-in capabilities that do not exist in the custom issue links you may choose to create.

One has to decide which do you value more: The flexibility to build custom hierarchies as you describe here (or may desire in the future), or the special built-in capabilities that Atlassian provides. 

Both have their pros and cons. 

Also, Structure has the ability to recognize and work with the special Atlassian links together with any custom links you may create.

It's your call of course, but I'd like to suggest you reach out to ALM Works (the makers of Structure) to further your assessment of Structure and learn what you can on this topic from our experts. 

Note that I am not saying Structure will do exactly what you describe above. In fact, AFAIK, nothing will.  As I said, you have to choose your own path. :) 

If you wish, you can schedule a session with our team via structure@almworks.com.

Hope this helps,

-dave 

P.S.  This Epic-Feature-Story vs. Initiative-Epic-Story: Which SAFe Hierarchy Should You Choose? article may be of interest to you. The author of the article, @Philip Heijkoop _ALM Works_, is one of the people at the other end of structure@almworks.com.