Any guidance here would be greatly appreciated...especially thoughts on my proposed setup of Portfolio.
We have upwards of 150 projects in our JIRA instance and are about to install Portfolio. Rather than adding the Portfolio custom issue type hierarchy to ALL 150 projects I proposed creating only 1 project that houses 2 Portfolio issue types (Portfolio plan source could easily use filters to retrieve the Epics and Stories desired AND the Portfolio issue types). This was my strategy which I tested and it worked:
With the following JQL I can return all the RPEs associated via Parent Link to the Product:
issue = <Product issue #> OR "Parent Link" = <Product issue #>
I wanted to put all the Portfolio issue types into 1 project to save all the admin time it will take to support those issue types in 150+ projects.
This worked fine...until the powers that be decided they wanted 4 Portfolio issue types in the hierarchy above Epic instead of 2; they want this:
Can anyone help me JQL that would allow me to search and return ALL the items associated with the Product issue at the top level down thru the RPE level?
Or am I way off base with my proposal of going with having the Portfolio issue types in 1 project instead of 150?
Thanks in advance for any help!!!
Unfortunately, it seems that it is not possible out-of-the-box.
Plugins like Scriptrunner may help you in this case.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs