How to change issue status for multiple projects?

[tommy-vti]

Select Topic Area

Question

Feature Area

Issues

Body

Hi!

My team's repo has multiple projects, and in our workflow we assign a single issue to multiple projects. We have projects to categorize work, and then bring them over to "sprint" projects when we get to them for the current sprint. Our projects use the same set of statuses.

One pain point has been that if we change the status of an issue on one project's kanban board, it does not propagate to the other boards. We have to navigate to each project and change the issue's status on each, which is painful.

Is there a way to effectively only change the status of an issue once, and have that status reflected in all projects?

Thanks in advance!

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[queenofcorgis]

Hi there - this is certainly a popular request and I've made sure to pass along your feedback, but we don't have a current way to do this automatically since custom fields are tied to each individual project.

Workflows could be used if there are actions that a status field change that you are using, such as an Issue being closed or a PR merging, etc.

Otherwise the quickest way to update them all at once would be using the Projects sidebar on the Issue page.

[tommy-vti]

Thanks @queenofcorgis !

Workflows could be used if there are actions that a status field change that you are using, such as an Issue being closed or a PR merging, etc.

My understanding is that this type of automation only works for closing issues. So moving issues to "In Progess" can't be automated. Is that right?

[goldiegadde]

We are running into this same issue , we use multiple project boards and an issue can live across multiple project boards. Update the status, priority and iteration for each project board is very cumbersome. Is there any plan to address this ?
Does anyone know of a GH action that can do this across multiple project baords ?

[TantienHime]

The challenge here might be that some projects don't have the same statuses. I can understand if you mark an issue as "closed" that it should automatically move the issue to whichever status in the project is considered "done". But in our case, we have projects with different statuses. Maybe there's a way to automate this in your repo? i.e., if this issue moves to "done", move them all to "done".

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[benmetcalf-rb]

+1 for this!

As different Projects can have different Issue Statuses, I agree that having this as default Github functionality would be difficult.

But if "issue > status change" can be added as an Action trigger for webhooks and workflow automation, then custom solutions would at least be possible.