Can we assign User Stories or Tasks from one Project to another project in JIRA ?

We are trying to use JIRA for Scrum of Scrums so from the Master Product Backlog, we need to assign User Stories or Tasks to other Product Backlogs (since more than one Apps are involved here for design & development and each App will have a Project and Product Backlog)

Presently there is no way I can assign a user story or task from Master Product Backlog to other Product Backlogs - it allows only assignement to Persons or group

End goal is to have a single view from Master Product Backlog / Sprint Backlog for the entire project

2 answers

0 votes

There is no assignment to group, so I'm not sure what you mean there.

Your backlogs would need to be changed to pull in the issues you want to see them in.  What are the board filters saying for each "backlog"?

Say, I have the Master Project and Master Project Backlog. The User Stories '@Master Product / Sprint Backlog are been worked by more than One Application. Now Each Application has their own Project and Product Backlog in JIRA. So the question is How can a story/task defined in Master Backlog can be assigned to the other Apps Project / Backlog ?

Basically from Project A's Product Backlog, we need to assign a task/User Story to Project B's Product Backlog

 

 

Please, you are not "assigning" - that has a specific meaning in JIRA, and it can be confusing for readers.

It's even less appropriate when describing how this works.

You have a backlog.  This is a *view* of some issues.  They are selected by a query.  You don't move things in to it.  You need to change them so that they match the view by being selected by the query.

So, again, what are the board filters saying for each backlog?

 

0 votes
Jack Brickey Community Champion Jul 28, 2017

@Sujith K Nivas,

FWIW, here is a scenario that may be similar enough that you may find it useful.

In a past life we had a resource shared across two projects. Each project had its own scrum board. One of the projects would occasionally need tasks worked from the shared resource. This caused us pain when trying to plan a sprint. We first tried simply under allocating the shared resource and found this produced poor reports for analysis. We then tried creating a dummy "project-b" task of say 10 story points to the resource and he would log time against it. That was cumbersome for the individual. Finally, after we sort of figure out how to use JIRA we simply updated our filters for the boards of each project to include the necessary tasks. Something like this...

project=A OR (project=B and assignee = Fred and...)

so while this may not be precisely what you are looking for it may help you establish a solution.

Bottomline - as Nic stated the solution, i think,  is in the filters for your boards 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 05, 2018 in Jira Software

Jack Graves: Real Ale enthusiast with a knack for Jira Software implementation

@Jack Graves [AC] first caught our eye with his incredible breakdown of what, in his opinion, can make or break a Jira software implementation. (Read his thoughts on this thread)! In this follow...

96,852 views 4 14
Read article

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