Create Sub-Task in Different Project from Parent Issue

Is it possible to create sub-tasks in a different project than the parent issue? We don't want numerous sub-tasks to throw off the parent issue sequences.

1 answer

3 votes

It is not possible. You might be able to do it with heavy JIRA customization but I wouldn't recommend due to the effort involved and possible issues.

Any way to affect the issue numbering? Something like: ISSUE-SUB-5

You would need dev work for this too. Again, this also can affect other funtionalities like rendering the issue keys as links in comments etc.

I completely agree with Jobin - there's no way to do subtasks in different projects.

Apart from the mass of coding and testing you'd need, it would be an organisational disaster too. I've seen it done (not in Jira) a few times, and it's an utter nightmare. If you really think you need to do this, then it's almost certain that your processes are a mess. Apologies if that seems harsh, it may well be working for you and I've only had bad experiences. But the projects I've seen it done in were chaotic and all failed miserably.

For the key changes, again, Jobin is correct - you'll need code, it'll be difficult, and it will break other bits of Jira unless you do a lot of coding and catch all the places that expect a more simple key (I imagine Greenhopper especially would be an utter pain to update)

hi,

we have the same need and i do not agree that this means the processes are a mess

we run software projects in jira and have a process fitting this need. the challenge is how to handle infrastructure tasks. we have an own infrastructure project intended for infrastructure tasks.

if noinfrastructure tasks are needed inside a sw project we either create inside the sw project but then the system admins have to work with several boards or we create in infrastructure ind link to a ticket in project but as well this is not great as you have to maintain 2 tickets..

so i wonder if someone has a solution for this problem. as well considering that the sw workflow normally differs from infrastructure workflow.

brg robert

You could think of solutions like https://marketplace.atlassian.com/plugins/net.customware.jira.plugins.createandlink. That way you'd keep the issues in different projects but keep a coherent linking policy. I don't see a simple way to do it in a single project...

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,304 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot