yep

Hi Ian,

Thanks for your question.

While hiding/showing tabs is a good idea it's not something that we want to invest in at this time. There are thousands of little good ideas such as this one, but at the end of the day we have a finite set of resources and this particular request has not been prioritised.

Rather than keep it open that we may one day implement it, we chose to be honest and close it so that customers have a clear indication on where we stand. For customers (not OnDemand) that really want this, they can use the third party solution or create their own customised solution.

Thanks again Ian and if you have any more questions feel free to contact me directly.

Cheers,

Roy Krishna
JIRA Product Management
roy at atlassian dot com

can you provide any insight into why this was closed as "won't fix"?

Hi,

I agree.

Since Jira does not support it at this moment, I'm using Customware solution bellow:

http://www.customware.net/repository/display/ATLASSIAN/Restricting+the+Change+History+Tab

And of course, I expect permissions not only for groups, but for any "resource" field in Jira, like Security Levels (and more): per user(s), per group(s), per role(s), per current assignee, per project leader, per component leader, per report and per custom "resource" fields, like per User/Group/Role Pickers.

Hi Mel,

It is not possible in 3.6.5 as the change history tab panel is hardcoded on the page. It was changed into a tab panel plugin and is available from 3.7.

Regards,
Dushan

Hi,

Is this manipulation possible/ safe on 3.6.5?

Thanks

Mel,

This is not scheduled at the moment.

However, in v3.7 this is a very simple customisation. Tab panels now implement IssueTabPanel:

/**
 * A comment, work log, changelog etc on an issue.  This plugin type is documented
 * <a href="http://confluence.atlassian.com/display/JIRA/Issue+Tab+Panel+Plugin+Module">online</a>.
 */
public interface IssueTabPanel
{
...
    /**
     * Whether or not to show this tab panel for the given issue.
     */
    boolean showPanel(Issue issue, User remoteUser);
}

And the existing ChangeHistoryTabPanel could be modified to do a permission check in the showPanel(Issue issue, User remoteUser) method. You could also provide a new custom issue tab

The only problem is that JIRA doesn't support custom permissions so you would need to piggy-back on either an existing permission, or check whether the user is in a specific group or project role.

This tab will become a little more complicated if we ever implement field level security

Is there any plans for having such a functionality enabled? Like a permission to view the change history?

Thanks

Mel

While this is a relatively new issue, I still feel it is an important one if JIRA is going to be used as a helpdesk. Therefore I am linking it to JRA-11125 and JRA-1330. We have external clients using JIRA and it would be nice if I could restrict them from seeing change history (and transition history although that's a user plugin). Essentially present a slimmed down version of JIRA without all the clutter. 90% of our users won't explore, but those who do will change their dashboards, and poke around where I don't necessarily want them to.

Terry,

Thanks for opening this.

A few reasons why we'd like to be able to have more control over the visibility of certain tabs, and the change history in particular.

First, we feel like our users should not be able to see any workflow changes. This should be reserved to the administrators. Users should only be concerned with the status of their issue and the updates to the actual issue, not necessarily its workflow. They might see this as some kind of "data corruption" which obviously is not what we want customers to see/feel.

Also it looks like there are redundant entries in the change history or too many entries for a simple action. We feel that it will prompt a lot of questions from inexperienced users who will probably feel a bit confused by all these entries.

The third reason would be that the dates and times of acknowledgment of the issues are important to us and should only be used by our administrators for reporting purposes. It should be at least possible to "grant" the permission to view the change history.

I hope this will help towards a change.

Regards

Mel