Avoid changing components field

[Rahul Aich [Nagra]]

Hi

On JIRA we use components to assign work to different teams.

Recently we observed that users are deliberately changing the components in order to improve their team's reporting statistics.

How can we avoid this scenario?

I understand with behaviors plugin i can make components field read only for our end users but behaviors plugin is buggy (even if you make it readonly, you can edit the read only field using keyboard shortcuts)

Rahul

[Jobin Kuruvilla [Adaptavist]]

Recently we observed that users are deliberately changing the components in order to improve their team's reporting statistics.

That's odd, especially when these things are captured in change logs!

Anyways, have you considered putting them only on Create screen and maybe also in selected workflow screens?

[Rahul Aich [Nagra]]

Hi Jobin

Yes i have considered as an option.

I am also considering the option of capturing the component modifications with emails with a different subject , is anything possible on these lines?

[Jobin Kuruvilla [Adaptavist]]

Not without throwing custom events and writing custom email templates. Some dev work involved.