As a Jira admin, I defined 8 sub-task issue types (verification, validation, document, etc.), when setting up an IEC-62304 compliant process for our start-up.
I want the sub-tasks in different projects (e.g. EPIC-1 has DOC-1 (sub)task), which does not seem possible. I explicitly want consecutive numbering of the 'EPIC' project, without interleaving of (sub)tasks for traceability.
So I think I need to upgrade the Sub-task issue TYPE to Standard (Task) issue type.
Can this be done easily, or should I just recreate the Issue Types?
PS 1. I'm setting up new projects, so I don't have to convert issues.
PS 2. as for plugins, I (only) have Scriptrunner.
Your assumptions are correct - what you currently have as sub-tasks cannot exist without a parent issue, which will break your numbering chain. If you want to create a consecutive ordering of issue keys with the same issue type, you'll need a single issue type in a project.
It's also worth noting that if you do decide to break out your work so that verification, validation, documentation, etc. each get their own project, then you won't necessarily need to use different issue types, since your projects will serve to differentiate the type of work being done.
As for converting sub-task issue types to parent issue types - that's not something that can be done. You'll want to recreate the issue types you want as parent issue types.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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