Eu preciso que o mesmo ticket caminhe por 3-4 projetos, mas não faço ideia de como fazer isso
Olá @Governança de TI
Você pode fornecer mais detalhes sobre o seu cenário?
Por que seu problema precisa passar de um projeto para outro?
Você pode descrever as etapas do fluxo de trabalho pelas quais um problema passaria?
---
Hello @Governança de TI
Can you provide more details about your scenario?
Why does your issue need to move from one project to another?
Can you describe the workflow steps that an issue would go through?
I need to create a workflow that walks between 4 projects, can you help me? I need the same ticket to walk through 3-4 projects but I have no idea how to do that
I need to create a workflow that walks between 4 projects, can you help me?
I need the same ticket to walk through 3-4 projects but I have no idea how to do that
For example, I have 3 projects: HR, recruitment and ITI need a workflow that goes through the three projects, starting with recruitment, moving on to HR and ending with IT
This would be my company's hiring process
Are all the projects Jira Service Management?
Are they all Company Managed, or are any or all of them Team Managed?
Do you actually want to move the issue from one project to another? That could impact any project specific reports that you have set up.
Have you considered creating a new, related issue in the next project when the issue reaches the end of the workflow in the preceding project?
Yes are they JSM Projects and company managed Can I create a trigger so that a new ticket is generated and moves the data from the old form to the next project form?
You could create an Automation Rule to do that.
https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/
For each project you could create a rule like this:
1 Trigger: Issue Transitioned Destination status: the last status in the workflow for the current Project2 Condition: Issue Fields Condition Field: Project Condition: equals Value: select your source project here3 Action: Clone Issue Destination Project: the project where you want to create the new issue Destination Issue Type: the type if issue you want to create Additional fields to set: If you need to fill in additional fields or copy data from fields in the source project to different fields in the destination project then you could do that in this same action.4 FOR: Branch / Most Recently created issue Action: Set Request Type You may need to update the Request Type field in the destination project for the issue you just created.
Because of the last actions (the For and Action) the rule would have to be a multiple-project scoped rule on the Rule Details page, and you would specify the source project and the destination project. Multiple-project scoped rules can be created only from the Global Automations page accessed from the gear icon (in the upper right corner) then selecting System / Global Automations.
Clone Issue will not copy any of the source issue's history or Comments, but you can elect to copy attachments. If you need the source issue's Comments copied to the new issue, extra steps would have to be added for that.
You would create a rule like the one above for each source Project / destination Project pair.
It looks like you're new here. Sign in or register to get started.
