nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to reset edit properties using Automation

Thomas Maenner_9p0yw8

Hi everybody,

in my workflow I'm setting properties to disable editing when the task is transitioned to done. They are:

I'd like to re-enable editing from time to time as admin, so I tried Automation using "Set entity property". For example:

Or:

But nothing works... The audit log is not very helpful...

Anybody knows how to achieve this in automation or any other way?

Thanks much in advance!

Tom

Accepted answers

All comments

Bill Sheboy

Hi @Thomas Maenner -- Welcome to the Atlassian Community!

The entity property key is plain text for that action, but you are trying to pass a smart value. Please try removing the double-curly brackets around the key.

Kind regards,
Bill

Thomas Maenner_9p0yw8

Thanks Bill, but didn't work...

Changed to:

Still getting:

Thanks,

Tom

Bill Sheboy

Thanks for testing that, @Thomas Maenner

Three more things to try (as I have not experimented with that specific property):

#1) Let's confirm what is actually stored for a work item with that property.

Using a browser tab, call the REST API endpoint for an example work item with the property currently blocking edits. The URL would be:

your Jira URL/rest/api/3/issue/BC-346/properties

Then find the property on the page to determine if you have the correct key name for it in the rule action. You are apparently putting that property specifically on the status, which I did not think was possible for a specific field...so the key may be wrong in the rule action.

If the key is there, open the URL for it to check the value and compare to what you expected.

#2) Rather than setting the value to true, clear the Property Value field instead. I do not know if this property is one where it is either false (i.e., do not edit) or empty rather than using true.

#3) If neither of those help, consider using the Send Web Request action and the REST API endpoint to delete the entity property rather than trying to reset the value:

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-properties/#api-rest-api-3-issue-issueidorkey-properties-propertykey-delete

Thomas Maenner_9p0yw8

Thanks @Bill Sheboy !

Tried:

https://URL//rest/api/3/issue/BC-345/properties/

Got

{"keys":[]}

Tried:

https://MY_URL/rest/api/3/issue/BC-345/properties/jira.issue.editable

Got

{"errors":{},"errorMessages":["The property jira.issue.editable does not exist."],"httpStatusCode":{"empty":false,"present":true}}

The set property directives in the workflow to disable editing work fine; so, the keys are correct. Besides, they are in the Jira support pages.

Tried the above with browser and curl. Weird.

2 and 3 didn't work either - a permission thing? I'm admin, but maybe something needs to be enabled.

Scratching my head...

Tom

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud