Can I automatically set PROJECT based on ISSUETYPE?
I started using automation recently. I have created a simple rule that will automatically set SUMMARY when creating a ticket based on ISSUETYPE:
- When: Issue created
- If: matches (Issuetype = X)
- Then: Edit issue fields (Summary = Xyz)
The above rule works fine.
I would like to set up PROJECT in the same way. I need one specific type of task to always be directed to one specific project (preferably when creating a task).
Unfortunately, the PROJECT field is not available for editing (I cannot create a rule analogous to the one described above for SUMMARY).
If anyone has an idea how to do it, please give me some hints. Thanks.
Project is not a field, it's an entire container for an issue. You can not edit it, you have to physically move an issue from one project to another.
The issue types available to a project are configured at the project level, so there's no way to choose an issue type before you know the project, as the project determines which ones are available.
You can however do "creating "Shopping" issue (no matter what project the user sets), I want to ensure that it goes to the SupplyProject".
Set up SupplyProject to allow the use of the "Shopping" issue type. Do not allow it to be used in any other project. The users won't be able to choose other projects after selecting the Shopping type (well, they will, but they will have to use a different issue type)
Well Edit issue operation is different from Create issue operation. When you edit an issue, it is already part of a project. This would be a move operation.
So in your rule when you create an issue, you will find a project field.
Is this what you want to achieve with your rule? Move an issue to another project?
Hi @Ravi Sagar
To be more precise, I am trying to create an automation rule analogous to the SUMMARY field (described above). That is:
I do not want to change previously created issues.
During the process of creating "Shopping" issue (no matter what project the user sets), I want to ensure that it goes to the SupplyProject.
"Edit operation" in this case is the action performed in the third step of the automation rule.
Like @Nic Brough _Adaptavist_ says...Project is not a field. and although you could create automation to move them all into the one project...why? When (as @Nic Brough _Adaptavist_ suggests) you can (and should) restrict that issue type to only that project. Thus routing people to it if they want to use it.
Users complain about "too many fields to fill", so I wanted to minimize the amount of interactions necessary when creating an issue.
After selecting issue type, I wanted the project to be selected automatically (specifically thist type of an issue should only be in this project).
@Nic Brough _Adaptavist_ 's advice should fix the problem.
“Organizations are made of people who create and follow processes which are constantly changing and are in need to be supported and nurtured… this is the spot where I realized I can br...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events