Avoid changing components field

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

1 answer

1 vote

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?

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?

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

20,948 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you