Managing joint Fix Versions and Releases for different project

[danny.shapiro]

We are using quite a few different projects, and a lot of times issues are joint.

For example - we have a project for our support team in which they are receiving and opening issues raised by customers.

Some of these issues are assigned to the core development team to handled, and are being addressed and released as part of the ongoing releases / versions.

I would like to manage and see these items as part of the Release page of the Core R&D team/Project, and also share the release notes from there.

Currently the only options I have is to use GitHub releases or move/clone these issues to the dev project. I'm really trying to avoid that.

Any thoughts?

We're using Jira cloud, and we have ~750 Jira users (only 150 are internal developers/product)

(BTW, buying an add-on and paying 800$ a month for this ability sound absurd to me)

[Petter Gonçalves]

Hello Danny,

I understand that you would like to display issues from the support team project on the release page of the Core R&D team project. Is it correct?

As you may know, Releases are not independent identities as Sprints, so it can only be added to the issues of the project it was created on.

That been said, we have a feature request created about this matter here:

- Create versions on multiple projects

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

Additionally, there are some workarounds provided by the customers in the feature request using plugins (Like Versions Sync).

As a possible free option, I would recommend using the Automation for Jira - Cloud Lite to automatically perform the clone option as you are doing right now. P.S: It have 300 free executions per month.

Let me know if you have any questions.