Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Receiving error on Automation for Assignee of a auto created subtask

I have been looking to set up a rule when transitioned a sub task is created and assigned to a user in a custom user picker field. This seemed to work fine at first, when trying to add some additional automation rules it then stopped. I have disabled all other rules and cut a shorter automation rule to allow this to run but I keep getting the below error message;

 

"Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -Assignee (assignee)"

 

I have set this to a global and a project level automation rule but still no success, I am not sure what was changed to cause this to stop working, the Assignee field should take from a specific user field and as mentioned this had been working previously.

2 answers

2 accepted

1 vote
Answer accepted

Answering my own question. 

Should have stepped back and taken a minute before posting.

I had amended the create screen and removed the assignee field as I wanted it to auto assign, this is why it wasn't processing

Steven

Wow.. I also made a ton of changes, one which included cleaning up the create screen.  It wasn't clear in the error that this was the issue, as the field was a common field on the issue type itself.  Thanks for saving me more hours of digging!

1 vote
Answer accepted

Hii @Steven Lloyd 

consider some items for running automation:

1. The actor of automation have assignee permission.

2. When you want create sub task which field is required and you must fill it by automation.

3. The actor of automation be in project role that has the first item permission.

4. On your sub task workflow check the conditions and validation that must pass to create sub task.

5. The custom field configuration must be include your project and your issue type.

if all these items pass please send screen shot of your automation 

Thanks for the reply Ashkan,

 

I was working with too much yesterday and changing little bits here and there so by the time it came to running through I didn't have a clue which change had impacted it, my own fault that one for trying to rush through it.

 

Cheers I appreciate the response as that too is correct 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

243 views 7 7
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