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

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

Issues with updating Security Levels

Hi

Hope someone can shed some light.

Background: We need to assign a security scheme to our project (and have done so) due to the confidentiality of some of the tickets coming in.  Our end goal is to set the ticket to one of the three levels in the scheme depending on the ticket Request Type. As I say, we have the security scheme all set up, and agents in groups assigned with different security clearance and this all works fine.

Issue: Using Automation for Jira I want to intercept the ticket on creation and assign it to the correct security level. The rule is easily created and looks fine. It never executes without error however:

  • If I do not set a security level default (eg default is "none") then the rule reports error "No fields or field values to edit for issues (could be due to some field values not existing in a given project)" even though the Security field is associated with the screen. So I cannot seem to populate what was an empty field with a value?
  • If I do set one of the security levels as default and try and update it on issue creation then the rule reports error "Condition failed because one or more issues failed to index in time".

    Indeed any random test rule that I try and run to do anything (eg update component) as a simple test when there is a default security level set will always return this error on an Automation for Jira rule that is triggered on When: Issue Created.

    So this seems something bigger and wider than trying to update the Security field; it appears one cannot use a When: Issue Created trigger on any project where a security scheme / with default set is being used?

Any help most gratefully received!

1 answer

Hi David,

Can you please try add a "re-fetch issue data" action after your trigger, and see if that resolves the issue for the second case ("Condition failed because one or more issues failed to index in time"). 

If that doesn't resolve the problem, then best you get in contact with us at support get to a resolution faster.  Can you please raise a support request here:

https://codebarrel.atlassian.net/servicedesk/customer/portal/1

Please include a screenshot of the rule, and also the audit log. 

Thanks in advance,

Scott.

Scott

Just back at work after some time off and grateful for your reply. I will have a go and if it's still not working, will indeed contact support team

many thanks

Hi, do you maybe happen to know what the solution was? I have the same problem but not with this addon. Thanks!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

🍻🍂Apptoberfest Update: Upcoming Virtual Events 🎉

Hello Community! I hope you've been enjoying the 🍂Apptoberfestivities🍂 (I know I have!) The event is heating up next week with a series of virtual events that we're calling the 🍻🍂Partner App ...

358 views 3 15
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