How to replace field data to star or strict it when write security data (issue update)

[ramiz omarov]

I need to add rules for issue updated. 
When user want to change for example summary to regex ( card number) , i want it to replace to star or denided.

If i did it with scriptRunner or automation in history it shown. 
That's why I want to strict it . 

[Andreas Springer _Actonic_]

Hi @ramiz omarov

Unfortunately, it is not possible for apps to make changes to the issue history on Jira Cloud due to API restrictions at the moment.

Our app Data Protection and Security Toolkit has been developed (among other things) for the exact use case you mentioned – to replace sensitive content in issues including the history –, and it works on Data Center, but not on Cloud.

We are currently evaluating a workaround for this and are looking for people to give us feedback on it. The workaround would be to replace the sensitive information, clone the issue in question, get rid of the entire history in the process and have a new issue that is completely cleaned.

I have described it in more detail in this form – please use it to leave your e-mail address if you are interested in discussing this further with us: https://forms.gle/FV7nbhstFw7m99pS7

Thank you!

[Tomislav Tobijas]

Hi @ramiz omarov ,

Can you maybe clarify this a bit more?

❓ If I understood correctly, whenever an issue is updated and the summary matches a specific regex, would you like it to transition to specific status?

Additionally, you'd like to do the transition automatically but for it not to be logged in the issue history?

I guess it would also be helpful if you could explain your process a bit further (how you manage these items at the moment) as maybe there're some alternative ways you can take to get the desired result. 👈

Cheers,
Tobi

[ramiz omarov]

@Tomislav Tobijas , 

My situation is that when changing the description or summary , the employee can add confidential user data there.
I need to solve this issue in jira cloud.
If when creating I can still add this to the validation, then when changing it is not possible, so that it does not end up in the activity - history.

Because in jira cloud , changes to the task occur on the screen (layout).

I need to somehow validate the changes so as not to allow him to change it to what he wants.

[Tomislav Tobijas]

Hi @ramiz omarov ,

Apologies for a bit late reply - the last few days have been hectic.

Anyway, I've played a bit with this a bit and the only solution I could come up with having these specific fields editable only on transition screens where you would have workflow validators that would check for an expression.

For example, let's say fields such as Summary and Description are only editable on create and status transition screens. 👈
On that, you can use Regular Expression Check validator to restrict transition if some of those fields contain a specific format (e.g. card number formatted 1234-5678-9012-3456).
*I've used the expression:

^(?!.*\b\d{4}-\d{4}-\d{4}-\d{4}\b).*

but AI is your friend here when it comes to writing regex.

This would result in something like this:

If a user tries to create or update these fields of which one or both contain this specific string format, they would get an error message and can't finalize the transition/creation. > Therefore, it wouldn't be added to the issue history.

I'm not sure if something similar to this is possible via cloud edit screens (without using transition screens). Potentially ScriptRunner Behaviours could help here, but I kinda doubt it.

Finally, I would say the best way forward would be to train users not to leave sensitive information in these/any fields 😅

Cheers,
Tobi

[ramiz omarov]

Hi @Tomislav Tobijas , 

Thanks for your efforts, and the first thing I said was that displaying user data in tasks should initially be regulated at the level of people's consciousness. And not control via Jira. Thanks again.