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
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,123 views 4 9
Read article

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