nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Initiative / feature / epic / story - can't get initiatives/features working properly

justmark

I read in a blog post that it is best to contain Initiatives and Features within their own project.

I've created a plan that has 2 sources (one for the project with initiatives and features), and the other containing epics and stories.

Initiatives are parents of features, and features are parents of epics (and the reverse child relationships are set up too.)

When I import all this into the plan, I see features with a (0) beside it even though there is an epic with stories attached.

Anyone here able to explain how they've implemented Initiatives, features, epics and stories successfully?

Thanks.

Comments

Earl McCutcheon

Hello @justmark ,

Thanks for reaching out, and as you mentioned the process of Adding the initiatives as a separate project is the recommended process when you are working cross project initiatives, but is not recommended in scenarios where you only need additional levels within projects individually as covered in "Configuring initiatives and other hierarchy levels" :

Adding the initiative level to multiple projects

An issue can live in a single Jira project. However, if your organization is working on several projects, you might want to consider having your initiative to span multiple projects.

If you're working with cross-project initiatives, you can create a dedicated Jira project, where the cross-project initiatives are stored, and then use the project as an issue source in your plan.

Adding the initiative level to a project

If you need more hierarchy levels in your project, and your initiatives don't span multiple projects, then you can choose to add the initiative level to just your project.

You can use this approach in cases where you need more hierarchy levels within your project, and when your initiatives will rarely be cross-project.

So depending on the approach you want to take either approach has its advantages.

As for the Hierarchies not showing the link from the first initiative level (Feature) to the Epics, this is odd, and a first step I would recomend checking the value in the Parent Link field on the Epic is correctly set to the desired Feature issue type.

To do this make sure that the 'Parent Link' field is included in either the View issue Screen or the Edit Screen for the project that the Epic is in, as covered in "Showing Portfolio custom fields in Jira" and check the value present in the field for the Epics that you are aware of that should be mapped to one of the features as its parent.

The Article also includes some additional points to check under the Expandable section titled "Conditions to consider..." int the Parent Link details section.

Check this out and let me know what you find.

Regards,
Earl

justmark

Hi Earl,

Thank you for your very detailed answer. It lead me in the right direction, and ultimately I got it to work.

I created an initiative and feature in a single project, and got that linked to an epic and story. Then I noticed the difference between what I had configured, and what actually worked.

In my incorrectly set configuration, the initiative and feature were set to "is parent of" and "is child of" rather than the "parent link". Once I saw the issue, it was very easy to resolve.

It might be a good addition to your online docs to specifically state note to use the "is parent/child of" linkages. Having a "Parent link" in addition to these link settings per issue is somewhat confusing though!

Again, thanks.

Mark

staceyking

Hi - does this solution work for the Cloud version of Portfolio? If not - is there a roadmap to bring in these same features into the Cloud version?

Thanks so much for the previous answers - they were helpful!

Earl McCutcheon

Hi @staceyking ,

Good question and Yes, the same logic will apply to Jira Cloud Projects linked to a Portfolio plan as well when dealing with cross project plan vs project focused plans.

The Portfolio documentation is structured slightly differently for the pages relating to Server and Cloud, as there are some difference in the application across the two platforms currently, but the cloud version of the doc that mentions this can be found as a child page of the "Configuring initiatives and other hierarchy levels" document at this link "How to add a new initiative level to a Jira project" noting the mention:

How to add the initiative level cross-project

An issue can live in a single Jira project but you might want your initiative to span multiple projects. If you are working with cross-project initiatives you can create a dedicated Jira project where the cross-project initiatives are stored and then use it as a source in your plan, then, follow the steps above to add the initiative.

And as the platforms are currently deviated in feature sets to go a bit deeper into the difference of the cloud and server versions of the application, that may help you out in the future if you are running into questions on Cloud vs Server capabilities; Cloud is currently running on Live Plans with feature parity to Live plans on Server, where Server has an additional capacity to use a New Planning Experience with the differences covered in the following documents discussing the feature parity changes that occur in the new experience:

And Portfolio on Cloud also has a limitation with the new Next-Gen project types detailed here:

Portfolio for Jira next-gen support

Also, a follow up question for both of you relating to where @justmark noted:

It might be a good addition to your online docs to specifically state note to use the "is parent/child of" linkages. Having a "Parent link" in addition to these link settings per issue is somewhat confusing though!

I do see a bit of confusion around the Parent link field in Portfolio regularly when users starting off and setting up portfolio, especially as the terminology has some overlap in various scenarios, EXE: a story is a parent of a subtask via the parent field, but the Epic is connected to the parent initiative via the Parent Link field, and is easily crossed in terminology, and I am looking to get the information reflected a bit more clearly, we do have a explanation of the parent linkage functionality documented here "Linking issues to parent issues", but this is a separate location than the other documents listed And more of a process explanation than a function one.

Also @justmark had noted working from a blog post do you have any feed back on where and why you were looking at that specific blog, and what the blog post was, as well as where you think would be the best place to add in the info about the parent link to the other portions of the documentation, and the blog post you were looking when you were thrown off during configuration steps noted, so we can look into an update to the content to clarify this a bit more.

Regards,
Earl

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

advanced-roadmaps