Project status field

[Joost van Maasakkers]

In our organization we use a project per client which we keep open while the client is with us. These projects can have two states: Implementation or Implemented/live. I would like to be able to show this information to our developers that are working on issues within these projects since this can affect their decisions.

Implementation: You can see this as a new client of which the platform is being prepared for use and isn't live yet.

Implemented/live: An existing client of which the platform is up and running with active users.

I could (mis)use categories for this and create a category for each state which would be fine but then I would like to get that category/state somewhere within an issue, is that possible? Best case: I would also be able to change the category in the issue I'm viewing (so it changes for the entire project, not per issue).

I've searched other questions and found https://community.atlassian.com/t5/Jira-Software-questions/Project-Status-Field/qaq-p/2369697 which comes close but the solution is not quite fit for our needs.

[Trudy Claspill · Accepted solution]

Hello @Joost van Maasakkers 

Welcome to the Atlassian community.

You could create a custom selection list field for this information and add the field to all issues.

You could identify one issue as the "authority" where you set the value. Each new issue created could inherit that value through the execution of an Automation Rule.

You could have an Automation Rule set to run when the "master" issue is updated, to update all the other issues in the project.

If you really want to allow the "authority" and all other issues to be changed by changing the value in one of the non-authority issues, you could use Automation Rules for that also.

The caveat here is that a change is being rolled out for how Automation Rules are counted towards the rule execution limit, and you might run up against that limit.

https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

Additionally, there is a limit to how many issues an automation rule can process in one execution. Depending on how many issues you are talking about, you could also hit that limit.

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

[Joost van Maasakkers]

Hi @Trudy Claspill ,

Thanks for your suggestions, I will look into that.