Hide fields in JIRA Agile? Allowing Customers to rank issues?

[Justin Hayes]

We currently use the Field Security plugin to hide various custom fields and time tracking data from our customers.

This has been fine while we've been using the standard JIRA view, but now the development teams want to allow the customers access to the Agile boards so they can rank issues etc.

The problem with this is that the Field Security plugin doesn't hide anything within Agile, and with Agile anyone can create their own boards and choose which fields are shown on the issue view. This means our customers would be able to access our hidden fields if they wished.

Has anyone else had an issue? If so how did you get round it?

We're considering one of the following which all have downsides:

1) Custom JS in the page to hide the options to add fields or create boards (could be circumvented)

2) Separate projects for the issues with protected data (mgmt overhead)

3) Internal and external JIRA's (synchronisation issues)

Thoughts and suggestions welcome!

Justin

[Justin Hayes]

Hi Justin,

Unfortunately it's not just time tracking we're hiding. There are various SLA, escalation, notes fields etc that we hide using Field Security.

[Justin Leader]

What about using something like Tempo to do the time tracking, and then restricting the users from accessing Tempo data. Would that work?