Hi Michael Mohr ,
Just one question: when status is done in your Jira side, and you face the sync error, which fields are you trying to edit? fields which are prohibited or which are allowed?
For better understanding, we can schedule the call if you want
Thanks,
Sonal
In status done workflow property for this status prevent edit of this issue. So all fields (beside of the comment) are read-only.
Changes are only possible in this state by a self transition for all fields that are on the screen of this self transition. According to Atlassian his is the only way in Jira to distinguish between fields that are editable and not in a status.
I would be fine with having a a online meeting that. How could I schedule a call with you?
HI Michael Mohr
Can you please share your availability on this ticket:EASE-22119 which you raised. I will get the notification from there.
Thanks,
Sonal
done
Currently we are facing the following problem:
The remote Jira on-prem instance has a final Done state in that edit is allowed for the issue.
But in our Jira on-prem instance Quality and Security departments prohibits edit in final states. Only the change of some fields are allowed in Done state, so that for this purpose we have configured a self transition in Done state with all fields being displayed on the transition screen, that are allowed to change in this status. With this workaround Jira allows to change exactly these fields even that general edit is not allowed in this status.
This different handling leads always to sync errors "edit in status Done not allowed" for sync events from the remote side when in finals status Done.
As we are not able to change these workflow settings on our side for only one project (because we are using shared configuration for all of our 3000 Jira projects). And we also aren't allowed to make workflow changes to 3000 projects only for one project.
Therefore we are asking here, if someone has a solution approach that somehow supports such self transitions in read-only state to change special fields.
Up to now we did not find a possible solution for that with Exalate, as Exalate seems to handle transition and field update separately and with that does not support changing fields that are on transition screens.
But perhaps you know a way to achieve a suitable solution for our problem with respect to the above mentioned restrictions.