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; } } }

Remove label from closed issues

Sandro Silva

Hi,

I've an automation that should delete a label from issues that are in closed or resolved status.
The question here is that the workflow does not allow changes once the issue gets to close or resolved status.

Is there a way that automation bypass this "restriction" and be able to delete a label from that issues?

Thanks.

Comments

andreas_qezsu8

Hi Sandro,

So Automation for JIRA actions still execute in the context of a user (the rule actor). We have to - since most of JIRA's internal APIs expect a user to exectue an action.

As such we are also bound by the same permission checks and validation that JIRA performs normally. So if an issue is marked as *not* editable by the workflow, then I'm pretty sure the 'Edit issue' action in Automation for JIRA will also not be able to edit this issue (and therefore can't remove a lable).

The only way around this I think would be to use security levels somehow instead of workflow to disallow editing of closed issues, so that only the Automation for Jira rule actor is in a security level that allows issues to be edited, and then setting that security level whenever an issue is closed. It's a bit complicated to setup though s not sure this is a great solution.

Hope this helps.

Cheers,

Andreas

David Fischer

Hi Sandro,

for your information, the JIRA Misc Workflow Extensions (JMWE) add-on doesn't have this limitation, neither on JIRA Cloud nor on JIRA Server. But you probably don't want to have to buy or subscribe to another add-on just for this.

David.

andreas_qezsu8

Hi David,

I'm curious, how do you get around this limitiation in Cloud? You'd have to use the REST API, which means you'll be subjected to JIRA's permission checks?

Cheers,
Andreas

andreas_qezsu8

Ah I see, because JMWE uses workflow post-functions, to edit the fields, which would require editing the workflow to set this up correct?

David Fischer

Hi Andreas,

yes, JMWE provides post-functions. But I'm not sure I understand what your question meant. We do use the REST API though.

David

Welcome!

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

Quick Links

Find more posts tagged with

atlassian-marketplace

addon-com.codebarrel.addons.automation