Post Function not clearing the field

[Tanya Fraser]

I have set the Remaining Estimate to clear using Post Function when the issue transitions to Complete but its not working.

I have confirmed that the workflow is being used for the issue.

I seem to have the correct permissions (I am a site admin, I have edit worklog permissions, edit the issue permissions)

I have checked the other issues logged, and cant seem to solve this. 

The issuetype scheme is being used for this project.

Any help appreciated - I have no other way to zero out the remaining estimates

[Jack Brickey · Accepted solution]

Can you try setting the value to “0”?

[Tanya Fraser]

Not sure what you mean - if  you mean manually changing Remaining Estimate to '0',  yes I can do that. 

But want to automate it because the team forget to do it, and I cant bulk edit the field.

[Jack Brickey]

No I mean using the Update Issue Field to set Time Remaining Estimate to "0".

[Tanya Fraser]

Thank you, that worked!!

[Reply Test Group]

Hi @Tanya Fraser 

did you give Browse Projects and Edit Issues permissions at the Jira automation user atlassian-addons-project-access ?

If you don't configure those permissions for your project, the Jira automation (the user that makes the actual change) won't edit a thing because it simply cannot do it.

When you ask to clear or edit a field, send a notification, create a ticket, etc, the change maker is always the Jira automation (if itself is not specified as the owner of the action, like the JMWE app in the post-function events).

Fabio

[Tanya Fraser]

Yes, the Browse Projects and Edit Issues permissions both have atlassian addons there.

[Reply Test Group]

Hi @Tanya Fraser 

ok, so if there is no Issue Security Scheme in your project (I presume that), and you have "atlassian-addons..." in the Permission Scheme, the only thing I think it may be the cause is that there are some proprierties in the status "Complete" which act as an additional filter and prevent users, groups or project roles NOT listed in these properties from viewing or editing the ticket for that particular state:

In my example, for the status "DEV ANALYSIS", I have 3 proprierties that filter who can edit the issue in this state: the project roles: Administrator, Atlassian Addons... and another role.

This means that, if there are 10 project roles listed in the "Edit Issue" permission, for this type of ticket in this specific status only the 3 listed in the status proprierties will in fact be able to edit the ticket.

Verify, maybe it's this ^^

P.S.: I put the Atlassian Addons guy in every permission of a project because I don't want to have problems with automations.

Fabio

[Tanya Fraser]

Thank you, I couldnt see any issue with properties - but changing the post function to using the Update issue worked.