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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation app user permissions in next-gen project

Hi!

I have created a Kanban next-gen project and set up an automation rule than transitions subtasks of a story meeting some criteria and sets some fields like assignee and start date.

The transitions went smooth yet the fields weren't updated. I think the possible reason behind this is that I am not seeing the Automation App User in any permission-related site.

I keep getting this error message: 

Unknown fields set during transition. Field may not be on transition screen. Fields ignored - Assignee (assignee), Start date (customfield_10015).

By the way, I have a free plan, I don't know if that affects the issue.

1 answer

0 votes

Hello @ortigozamatias

Thank you for reaching out.

The error you are facing when executing the Automation to edit issue fields in a Next-gen is usually caused by the fact that Jira Next-gen uses unique entities.

Explaining better, Next-gen projects do not share statuses, schemes, or fields with other projects. Each Next-gen project has its own set of fields that are not shareable with other projects, however, the same name can be used to identify those fields, so you can add the wrong field to be edited in the Automation rule.

We have a feature request to improve this behavior:

https://codebarrel.atlassian.net/browse/AUT-1853

To fix the automation, please check if the "Start date" is an existing field in your Next-gen project and if you are not selecting a field from another project with the same name in the automation action. 

If that's not the case, could you please provide us with a screenshot of your automation rule so we can further troubleshoot the problem?

Let us know if you have any questions.

Hi @Petter Gonçalves

Thanks for the reply.

I understand what you say, I'll follow the progress on that matter. 

Today I tested the automation again and everything was correctly updated. However, I keep getting the error message in the audit log.

Here are some screenshots of the automation rule and the story configuration.

 

Screen Shot 2020-07-28 at 3.28.59 PM.pngScreen Shot 2020-07-28 at 3.29.35 PM.pngScreen Shot 2020-07-28 at 3.29.56 PM.pngScreen Shot 2020-07-28 at 3.31.22 PM.png

As I have said, all the fields both for the story and its subtasks were updated accordingly, but the error remains the same,  which I repeat below:

Unknown fields set during transition. Field may not be on transition screen. Fields ignored - Assignee (assignee), Start date (customfield_10015).

 

Let me know if you need anything else.

Best!

Hello @ortigozamatias

Thank you for the details.

I see that in your Automation rule you are setting the fields Assignee and Start date for your sub-task issue type, however, the screenshot you posted is related to the Story issue type screen, not sub-task.

Can you please confirm if the screen related to your sub-tasks are properly configured with both fields?

Additionally, I would like to say that Next-gen projects have some compatibility problems with Automation for Jira since it has a different architecture and many features work in a different way.

We have a feature request to fix those compatibility problems in Next-gen:

NextGen Software projects are fairly broken in cloud 

Please, refer to the link above if you face any other strange behaviors with Automation and Next-gen.

Let us know if you have any questions.

Hi @Petter Gonçalves 

Yes, I've forgotten to check that.

Here it is the snapshot:

 

Screen Shot 2020-07-30 at 6.56.20 PM.png

If there isn't something I can do to make it work I'll leave all the rules created and wait for the fix to be implemented. I really look forward to that since this feature improves the workflow quite a lot.

Thanks for your help.

Best!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

165 views 0 4
Read article

Community Events

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

Events near you