OK, here's the situation:
My stories have a link that is "Linked Issues" and the selection is "is sponsored by" and then we link to the portfolio epic that funds that story.
I need to update many stories with that information, but I don't know how to do it via a bulk change instead of going one-by-one. This is not a field available.
Anyone can shed some light here?
I'm no specialist on Portfolio features, but it seems the key problem you are facing here is that you are not been able to return in a JQL query all the issues which have other issues linked as "is sponsored by".
Have I understood it properly? Or the problem is that you are not been able to find the edit options you want using the bulk operation feature?
If you are talking about a JQL query, it is not possible to return linked issues based on the type of link using only JIRA, but only using a specific issue as the source of the link.
The only way to return this kind of information would be by using a plugin like JQL search extensions which provide you with the parameter issuesInQuery that you can use to return linked issues that match specific criteria. E.g:
"project = NSPPORT"
Let us know if I have properly understood your question.
Thanks for your attention to this.
The JQL I currently use to see all the issues related to a particular Portfolio is the childIssuesOf(""). Example:
id in childIssuesOf("NSPPORT-xxx")
That returns all issues under that specific NSPPORT.
The problem that I'm having is that just recently we started to use the link "is sponsored by" and there're a lot of active issues that need to have this information updated, but I don't see it as an available field to perform a bulk update. Is this even possible to be done as a Bulk change?
Thank you for your explanation. Now I understand that the parameter you would like to change in the bulk operation is the linked type and linked issues of the ones returned in the JQL query.
Unfortunately, JIRA does not have this kind of functionality in the bulk operation feature. We have a feature request opened to implement it:
Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.
Let me know if you still have any questions.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events