Can I create a rule that will move an issue to another project based off of the status? I have created two project of which I am the project admin for both. Both are software projects. I am trying to configure a rule that states when the status has changed to Review to move it to another project.
Context: I need the issue to be reviewed and approved in another board so it does not track against my team's sprint and I can mark our release as completed. When I previously created another board the release and issues remained tracked in our sprint as well as in the release. An agile coach recommended the creation of another board, link the boards, create the rule move the ticket out of the board and the release upon sending to project 2 and create query or a dashboard that combines the tracking of both projects in one view.
Hi @Robin Hannah ,
I am assuming that you are referring to "Automation" available in Project Settings in Jira Cloud. As of now, I do not think it supports moving issues to other projects.
Coming to your context, just want to understand who is the person responsible for reviewing and approving the user stories? Can he/ she be any person in your team? Or is he/she usually a fixed person?
Can't the review process be separated from the execution process?
@Deepanshu Natani Thank you for responding. Yes, I am referring to automation. I am the person responsible for approving the users stories for the Agile team. The other board is for approvers from the customer/product side and consist of several people.
Since JIRA does not support automation of moving between projects my back up plan is manually perform the function myself. There only select tickets these approvers are required to review. In the event the approver needs to return an issue I can create a bug in the dev board and link it to the issue for historical/tracking purposes. I was just looking to streamline where possible.
Again, thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Robin Hannah ,
If your question has been answered correctly, please mark the answer as accepted since this may be useful for members having similar query in future. :-)
Also, I would really like to understand have you created a separate project just for unapproved issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Deepanshu Natani Thank you. I have a service being certified by my team, we have two other teams that will validate the certification and approve the push to production. I want to track our sprints and work separate from the validation and approval as our work is considered complete unless there are bugs. When I created two boards with two different workflows in the same project, the issues remain tracked in the sprint. My solution was to create separate boards. Although it seems like I could have set the resolution when it came to me on my board and still track it in the separate board, I am unable to do that as all of our issues will not go to the approvers and I needed to set the resolution for Done on the board for those. It gets complicated. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.