Avoid let issue editing only to Exalate plug-in if a field is populated

[Nicolò Spito]

If in a project I have both tickets synchronized from another instance by Exalate and tickets created manually in the current instance, I would like those created by Exalate not to be manually editable except the comment.

Is there a way to avoid manual editing from user if the ticket come from Exalate plug-in?

[Matthias Gaiser _K15t_ · Accepted solution]

Hi @Nicolò Spito

welcome to the Atlassian Community.

One solution I can think of is to modify your permission scheme and modify your Exalate sync accordingly. I have these steps in mind:

• Generate a new Group Picker custom field which by default contains a group with all the users who should get access to the usual tickets & configure the field for the project.
• Setup your permission scheme so that only people which belong to the groups in the newly created custom field have "Edit Issues" permission.
• Modify your Exalate synchronization so that it removes the group or sets a more restricted group so that your users can't edit the issue.

How does that sound?

Cheers,
Matthias.

[Nicolò Spito]

Thank you Matthias for the kind response!

The only difficulty is that "Exalate" is not a real user that I can add to a group.

I was hoping to be able to intervern with Jira automation:
When the ticket has EXALATE as a reporter, then disable changes for everyone except EXALATE.
Maybe using the properties.

What do you think?

[Dhiren Notani_Exalate_]

Hi @Nicolò Spito ,

I am Dhiren from Team Exalate.

Yes, I think that you can try using Jira Automation for this purpose and make fields read only somehow when the tickets are created by Exalate user.

Also, may I ask you why do you want to disable any manual update?

Is it because you want to make your sync uni-directional?

Thanks,

Dhiren

[Nicolò Spito]

Hi Dhiren and thank you!

Synchronization is only one way and it is right.

But I want to prevent a user from changing anything thinking the change is valid. (I know that any change will be overridden at the next synchronization but the user does not know and it can cause misunderstandings.

[Matthias Gaiser _K15t_]

Hi @Nicolò Spito

you're right apps are not real users which you can manage in groups unfortunately. But you could setup your permission scheme so that the Project role (atlassian-addons-project-access) is always able to edit the issue. The exalate user should be part of this role.

When you're talking about properties, do you mean workflow properties? Unfortunately, I don't see how they can help since they are able to prevent editing based on the state instead of who is doing it across all states.

I'd still recommend my approach from above. You could setup an Automation (or possibly use Exalate) to clear the group picker when Exalate is the reporter or a synchronization happened.

Hope this helps.
Matthias.