Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Convert (upgrade) Sub-Task Issue Type to Standard. The TYPE not the Issue(s).

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.

1 answer

1 accepted

0 votes
Answer accepted

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

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...

315 views 9 7
Read article

Community Events

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

Events near you