Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Unclear error when creating a task via automation

Nofar Ben Kereth October 11, 2022

Hey,

 

I set up a rule that created a task in a Personal project (my, i'm the admin there). But it shows a weird error I can't understand. 

Screen Shot 2022-10-11 at 12.08.27.pngScreen Shot 2022-10-11 at 12.08.36.png

4 answers

1 accepted

2 votes
Answer accepted
Nofar Ben Kereth October 11, 2022

Found the solution - when I specified the issue type instead of choosing "Same as" it worked 

0 votes
Nofar Ben Kereth October 11, 2022

It seems the problem is in the source project as the IDs in the error belongs to it. Any suggestions?

0 votes
Dan Tombs
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 11, 2022

Hi @Nofar Ben Kereth

 

Does the automation actor have access to the project? If it is using the standard automation user, then make sure the apps role has access to the project in the permission scheme.

Dan

Nofar Ben Kereth October 11, 2022

The actor is Automation for Jira - how can give it permission? Doesn't it already have it by defualt? 

Dan Tombs
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 11, 2022

@Nofar Ben Kereth

Can you send a screenshot of the permission scheme. Specifically browse project and create issue permissions.

 

Dan

Nofar Ben Kereth October 11, 2022

Since its a Personal Tasks project, it doesn't have a scheme. Adding the Access settings Screen Shot 2022-10-11 at 12.24.59.png

Dan Tombs
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 11, 2022

@Nofar Ben Kereth

Switch the automation actor to you to see if this resolves the issue.

Dan

Nofar Ben Kereth October 11, 2022

Just switched to myself and same error shows.. 

0 votes
Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 11, 2022

Hi @Nofar Ben Kereth ,

Please check if you have same ticket type in NOFI project as similar to that you created in Your personal project. 

i.e.

  • If you create BUG ticket in your personal project, then NOFI project should also have BUG ticket type
  • If you create TASK ticket in your personal project, then NOFI project should also have TASK ticket type
Nofar Ben Kereth October 11, 2022

Thanks.

Yes, both have Task and this is what I was trying to create. 

Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 11, 2022

@Nofar Ben Kereth ,

  1. Please check if there is any mandatory/required fields in destination project that are not being filled from automation.
  2. Check if the automation rule actor has create ticket permission on the destination project. 
  3. Check if there are any other conditions/Validators in destination project ticket type workflow.
Nofar Ben Kereth October 11, 2022

1. No mandatory/required fields

2. The rule actor is Automation for Jira, as far as I know, you don't need to give it special permissions.

3. Nothing..

 

The only thing I can think of is that the destination project is a Personal Task type.. 

Rilwan Ahmed
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 11, 2022

@Nofar Ben Kereth 
You need to add "Automation for Jira" user to create ticket permissions explicitly in your project. You can go to permission checker and see if user really has the permission or not

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events