I have a strange requirement wherein i want a sub-task of some issue of some project to appear as sub-task/issue in another project such that it remains the same sub-task in both projects so that any updates to it by another project should reflect in it in original project as well. Logically speaking i don't want to migrate it to another project. I just need two instances of it in 2 projects so if i get a sub-task created in my project and its relevant to another project i canreplicate it for the other project and should be able to see updates from my own project.
Please help me on this.
A sub-task has to be in the same project as it's parent, so you can't do this.
The closest you can get is to clone the subtask, then move it to the other issue, but that really does create a completely separate issue which will immediately diverge from the original. The manual process on the split and move is complex enough, and quite hard to script.
I'd be thinking of other ways to get your users to collaberate on the sub-task...
Um, my suggestion was that you have a look at how else your users can collaberate on sub-tasks. Without knowing your organisation and seeing how it works, I can't really recommend much more than talking to each other about how you want to work!
Actually we'll be having few projects that will be having their specific roles/functions.
Like Project A is main project where issue is created, Project B deals with user administration issues, Project CV deals with jira customization issues,etc
So if request comes to Project A in form of isssue and subtasks are created to that issue we would like specific sub-task to replicate under some issue or as just issue in anorther project say B or C whose role matches wuith the sub-task (could be user administration).
I hope that answers your question.
Hoping for suggestions from you on this.
To merge projects, filter for "project 1" and then use "bulk edit" to move all the issues into "project 2"
You should really check that the projects are compatible first though - if they're using all the same schemes and fields, you'll be fine, but if there are differences, you'll need to scan them to ensure they're compatible.
You could also take a look at JIRA Agile and create Epics in Project A and add the issues in Project B and Project C to this Epic (Epics span across projects so that's possible).
Otherwise you could simply use issue links instead of subtasks.
Or like Nic suggests: merge all your projects together and use different issue types, or simply different assignees.
Could you also provide me some solution to the question i asked regarding:-
Want external user to be added as user in jira automatically without jira-users permissions.
please search this in the search bar and you will see under my name this question asked recently. I would very highly appreciate any solution/answer to this from you all.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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!
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