The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Track Issue Status for Multiple Releases/Deployments with One Issue

İbrahim Ebeler
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 6, 2024

Hi community,

We are currently using JIRA Data Center.

We want to be able to track status of releases for multiple environments (customers) on a single JIRA issue.  We are developing a feature in product which is described under a single issue and after development completed (development deployed), we are releasing to multiple environments (customers) on different dates. So, we have a feature released to some environments but not yet released to remaining environments. We want to be able to track that in relation with the issue.

We also want to be able to package a group of issues since they construct a main feature together. What I mean by "packaging" is that; we want to be able to transit the status of all these issues (in the same package) jointly, with one transaction/process. We do not want to progress each issue separately.

Hope to find a solution here, thanks in advance..

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Brant Schroeder
Community Champion
October 25, 2024

@İbrahim Ebeler welcome to the Atlassian community

I would suggest creating an epic for each release and creating an issue for each customer associated with the epic.  Create a workflow that follows your release cycle.  You can sync statuses on issues with automations.