Hi,
I'm trying to setup a specific structure in which we have different projects with regular stories and a Jira projectX with only features.
In our operational context, it's mandatory to have 4 specific stories always linked to the ProjectX.feature via the Realized by relation.
And I want to be able to follow-up the existence of the 4 stories.
Some context will make it more clear:
I'm having Jira projects projectA, projectB and projectC with regular stories.
And a Jira projectX with only features (~Portfolio project).
Features in ProjectX are REALIZED BY StoriesProjectA, StoriesProjectB & StoriesProjectC.
My structure should display the following hierarchy:
FEATURE1-PROJECTX
--->Is Realized by: Story1ProjectA
--->Is Realized by: Story2ProjectC
--->Is Realized by: Story3ProjectB
--->Is Realized by: Story3ProjectB
FEATURE2-PROJECTX
--->Is Realized by: Story1ProjectC
--->Is Realized by: Story2ProjectB
--->Is Realized by: Story3ProjectC
--->Is Realized by: Story3ProjectB
FEATURE3-PROJECTX
--> No - Is Realized by: Story
Currently my structure automation looks like this:
2nd: Group each issue under issue that is Realized by it
1st: My insert JQL query= Project in (projectA,projectB,projectC) and issuetype(story)
This provides me a structure with 2 problems:
I do get the above hierarchy but,
1. without the FEATURES-PROJECTX with no REALIZED BY relation
2. I'm not able to add " GROUP BY" -> STATUS: This results in grouping by the STORY Status.
Does anyone know how to solve my above 2 issues ?
Many thanks!
Hello @Alex Agn ,
In your scenario, are there Stories that do not Realize a Feature and need to be included in the structure? If so, would you mind if those Stories exist on the same level as the Features?
My thought here is that you could modify your JQL Insert Generator:
(Project = "ProjectX" AND issuetype(feature))OR
(Project in (projectA,projectB,projectC) AND issuetype(story)AND issuelinks != "Realized By")
The issuelinks != part may need to be adjusted using the workaround described here.
You can then use an Extend Generator to add the Stories that Realize your Features.
The idea is that the Inserter will add all of your Features, regardless if they have any stories assigned to them, as well as stories that are not assigned to Features. The Extend Generator will add stories to those Features that do.
I hope this helps.
Best,
David
Hi @Alex Agn ,
Structure plugin relies on Jira core system issue relations.
To ensure you have multiple projects get displayed in single structure board, you need to maintain a symmetry.
Populate the data with query.
Group by
Instead of feature issue type, you can use epic.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.