Can I connect a board column from one project into a different projects backlog?

[Ibb]

Hi I have two different projects, one is where the developers are working at and the other one is where the project managers are planning new tasks to the developers.

What I would want is that I want to have one column in the projects managers board that is called "ready for develompent", and whenever they drops an issue into this column it automatically gets transfered to the developers next sprint and backlog.

But I would also want the ex. 1.6 V of projectmanagers sprint to be connected to the V.6 of the developers sprint, and next 1.7 V for 1.7V and so on. 

Is this possible to do, it is in the same organization. The two different projects are also created in Scrum.

[Ibb]

Hi @Trudy Claspill
thank you for your helpfull answer!

The developers are working in a company managed project and are the ones who firstly started to work with Jira. I created the project managers project in a team managed project. I have full control over the project managers project and could create a new company managed project instead for the project managers. However I do not have full controll over the developers company managed project. 

Would you suggest that I should create a new company managed project for the project managers instead?

The idea is so that the project managers could create issues for the developers that ends up in the developers backlog of chosen sprint. Is this possible? Because I would not want to create issues inside the developers project that ends up in the project managers project if you understand what I mean. I want the other way around that would say from project managers -> to developers.

Thank you alot for your help. 

[Trudy Claspill]

Hello @Ibb 

Welcome to the community.

Are you working with Team Managed projects or Company Managed projects?

An issue has a workflow that indicates the Statuses it transitions through. If the issues are in different projects and the projects use different workflows for that issue type, then you can't really have that one issue running through two different workflows in different projects and in different sprints.

I recommend that you look at using automation to create a new issue in the developers' project that is a copy of the issue from the project managers' project and link the issues together. That would get it into the backlog of the developers' project.

Within the Automation Rule when you are creating the new issue in the developers' project you can also set the Sprint field. There is a Next Sprint option that you can use (you have to specify the board in which that sprint was created). If you have multiple planned sprints defined in the developers' project board I'm not sure if Next Sprint will get you what you want.

In the example below you would set up the rule to run against the project managers/ project, and then in the Create Issue component you would specify the developers' project as the project in which the new issue would be created.

For copying the information from the source issue you would set fields in the destination issue to smart values, using the {{triggerIssue}} object to get the data from fields in the source issue.

[Ibb]

Hi @Trudy Claspill
thank you for your helpfull answer!

The developers are working in a company managed project and are the ones who firstly started to work with Jira. I created the project managers project in a team managed project. I have full control over the project managers project and could create a new company managed project instead for the project managers. However I do not have full controll over the developers company managed project. 

Would you suggest that I should create a new company managed project for the project managers instead?

The idea is so that the project managers could create issues for the developers that ends up in the developers backlog of chosen sprint. Is this possible? Because I would not want to create issues inside the developers project that ends up in the project managers project if you understand what I mean. I want the other way around that would say from project managers -> to developers.

Thank you alot for your help. 

*Saw that I had put this an as answer to my own topic when it should have been an relpy to you.

[Trudy Claspill]

My suggestion applies to your scenario. It doesn't matter that the issues are in different types (Team vs. Company) projects. You don't need to create a Company Managed project for the project managers'.

You define the Rule to be triggered by transitioning issue only in the project managers' project, and set the action to create copies of the issues in the developers' project. If you construct the rule correctly it will not create issues in the project managers' project based on issues in the developers' project.

Do you want to allow creation of issues directly in the developers' backlog without a corresponding project managers' issue?