We typically use links instead of subtasks unless the subtasks are very small, mostly because you have to have separate types for subtasks, i.e. a bug is a type, a bug which actually needs 3 separate fixes, would require Bug type tickets, and Bug-SubTask types.
In any case, I don't see a good way to bulk operate on linked tickets. Subtasks have the little "meatball" menu which allows bulk editing.
I'm not sure what you mean by meatball menu - do you mean the breadcrumb icon (3-dots) where you can select to bulk modify sub-tasks in an issue?
If yes, you can bulk edit from a filter also. You will need the global permission "Make bulk changes" - and edit access to all the projects the issues live within.
----------------
Search:
First, search for linked issues - your options in standard Jira are:
issue in linkedIssues("ABC-1","is blocked by")
issue in linkedIssues("ABC-2")
^ This searches for all linked issues against one specific issue. You can specify the link type (like in the first example) or get all link types by removing the "is blocked by" (like in the second example).
Or...
issueLink = ABC-1
^ This find all issues linked to this issue of any link type (including sub-tasks). The good thing about issueLink is you can use it to find linked issues of multiple issues using IN.
You can specify the link type in this option - either in issueLink or using one of the specific link type searches - for example, below are both examples to find issues that block ABC-1.
There will be a good number of issue search types like "issueBlocks", depending on the link types configured in your instance:
issueLink["blocks"] = ABC-1
issueBlocks = ABC-1
Or...
issueLinkType = "is blocked by"
^ Find all issues within a specific link type. You could refine this to a specific project or similar to limit the search if all issues in you instance is too wide.
For more information on JQL field and function options, see the advanced search field reference and function reference.
----------------
Bulk Change:
Once you have your search results:
----------------
If this isn't what you meant - let us know, and we can advise further :)
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.