Can a decision made 10 years ago be revisited?

none of the Workaround links in Description work. Can you please update the links? Thanks.

@Shlomi Hazan, I'd suggest reading further back through the conversation for all the reasons it's not going to be done, and the options for implementing something to help out (Also note that "it's been 13 years" is not any reason to do something)

@Joe Ferarra 

This issue was raised 13 years ago, I think it is enough time to find a solution don't you think

@Shlomi Hazan

That plugin may have taken a long time to develop.

@Giacomo Kavanagh

That's absolutely correct, they feel that the time spent to develop it doesn't justify the "payout" and thus are making an intelligent business decision.

They can do it, they just don't want to.

I'm still hopping that you will reconsider.

How come you can't do it but you point us to a plug-in that can handle it?

Thats the GREAT pity. Albo pitu pitu

I'm watching this issue since 5 years

What a pity !

Jack, it is "done", if you look at the status. Atlassian are not going to implement it.

Hi,

Could you let me know when this is done please?

Thanks,
Jack

The inability to restrict field permissions in Jira Cloud creates a huge SOX compliance gap for us. We've implemented the workaround where Edit is disabled and replaced with an interstitial workflow screen, but that solution is so hackish.

+1

This really is a necessary feature to our team. We should be able to prevent prevent a group of users or project role from editing default or customized issue fields via workflow.

Removing comment - generally unhappy with Jira

Hate to pile on, but I'm going to... This really is a necessary feature. In your original status comment, you mention implementation would make Jira administration more difficult. I submit it is not having this feature that make using Jira difficult.

Really need this Field level security for our Jira on Cloud. Most of the AdOns do not apply to Jira on cloud.

So please help or provide some ad on.

Hi, I'm using Jira 6.3.13. Is there a way to limit a custom field to be viewed by certain groups/users, the same way the Comment field is?

+1

We are serving different customers for IT.
Not having field security means that we need a separate xls or googlesheet tracker for tracking internal time of resources working on tickets. Surprising how we can achieve tracking simple information which should not be visible to customers. We do not need elaborate tracking at all.
Is there any way JIRA provides way to track simple information (text, numbers) which are not visible to "service desk customers" ?

+1

We need field level permissions too on our cloud instance

+1

+1

"We have reviewed this request again within the team and have had long conversations with our JIRA architect. This has lead to the conclusion that the original reasons for not implementing this feature still apply."

Roy Krishna
JIRA Product Management

Based on what you're saying you made a purposeful decision to not implement this feature when you originally designed the platform and you still feel that this original vision is a valid approach. I'd be interested in understanding why as it would help me make a more informed decision about how we use Atlassian products in the future. Am I to understand that Jira will never ship with built in field level permission or even more specific the ability to turn off all time tracking / worklog features for a specific role?

thx

+1

+1, this is something we could use as well!

+1

Sorry, I didn't notice "Won't fix" reason - then right.

Why? Because the answer is BS. This is clearly a matter of extreme importance to many people and the door has been slammed in our faces. The hope is that maybe if Atlassian decides to listen to us one day they may reconsider their position on this issue before we reconsider our positions on license renewal.

Why you people make mess by adding this +1 meaningless comments? Why not using "vote for this issue" button?

+1

+1

There's no way to do it on Cloud at all - even if you could hide fields with javascript in the issue view (and I don't think you can on Cloud) the information is still in the html, still available over REST and will still show in searches and lots of other places.

Hi Daniel,
We have implemented cloud verison JIRA and I am looking for same field level security (basically to hide a cost field from vendor team) - can you please tell me if you found any cloud plug in to implement?

+1

The JIRA web interface isn't the only way a user can interact with JIRA tickets.

Chris - I don't think it's simplistic for this request. I am attempting the same exact thing and...if I could simply configure the fields on the create screen and associate that screen in the Screen Scheme based upon user groups (in this case the Client group) this would in fact solve the objective. And no, they would not be able to enter say 'priority' (or severity level in our case of the customized field) if the field didn't appear on the screen (i.e. if you don't see it you can't enter it). Not sure what you mean by 'the API' in this context. I simply want a way to specify different screens (that I have created) with different fields for Create, Edit, View in the Screen Scheme by group. It's done exactly that way now, except you can only specify one Create, one Edit, and one View screen (configured with whatever fields you'd like) to be associated with every user in a Screen Scheme - and as stated - if you don't include a field on one of those screen you can't enter data into it. So in essence - if you can't see it, you can't edit it. Works that way now - all I'm asking is to expand what's already there.

Perhaps you haven't created different screens for Create, Edit, View and associated screen schemes.

This solution would simply allow you to specify multiple screen

I think it is a little bit simplistic to say that "if you can't see it, you can't edit it"... there are other things to consider, eg. the api. I agree with the sentiment though... work with your customers to give them what they want.

Ugh...that was supposed to say "and as a_ result _you've abandoned it"

Bottom line - just work together to find a solution that will accommodate the requirement or at least the fundamental business need....don't assume it requires 'field level permissions' or that's the only path you'll go down.

Simplicity is a thing of beauty!

You guys are making this was too complicated and as a realist you've abandoned it. You don't have to create field level permissions - quite honestly nobody enjoys the maintenance of such a solution. The business requirement is that when external customers are given the access and flexibility to create issues within a project in JIRA, the project owners would like to control what they see and what they can enter. If someone can't 'see' a field they in essence do not have permission to enter data into the field....therefore, how about just implementing something like: Group Level Screens within a schema...Client Group sees Create Issue (Client) screen when logging in....Internal Group sees Create Issue (Internal) screen when they log in...same for Edit and View.

This has to be exponentially less complicated (from both a development and configuration / maintenance stand-point) than approaching this from the Field Level Permissions perspective.

+1 ....

+1 (Seriously!!)

+1

+1

+1

+1

+1

+1 Would be awesome

+1 000 000 000

+1

vote don't work.
Issue is closed.
+1

I understand the importance, but you should click on vote instead of these +1 comments. Less spam Thanks

Neil, this is an important feature for enterprises, regardless of the impact, it is weird to find third party plugins that provide this feature, while JIRA developers can't...
+1 (again)

I don't think all the +1s in the world will change their mind, they've clearly stated it will not be done and described the effort and impact to the system, If I take them at face value of super complicating the admin and taking 12-18 months to do a ground up rewrite is not feasible for any development team for one feature, would you want your own dev teams to be hijacked like that?

+1

+1

+1

+1

+1

+1

+1

+1

+1

I still support this request...after eight years of using Jira

@Atlassian: From a customer perspective @rachel.grimmelmann is right. I support her request. +1

@Atlassian, if this issue was originally raised twelve years ago and folks are still demanding it today, it is worth looking in to again. Please!

Thank you,
Rachel

Hi fellows,

long time no update for one of the most important JIRA issues.

We switched from Server to Cloud and oops there is no Field Security Plugin anymore. So time tracking and estimations are visible to our clients now. Is there any way to workaround this for JIRA cloud?

@Atlassian - I like the products and the support very mutch but this issue shouldnt be closed. It should stay open until the DEV team finds a suitable solution.

Thx for any fresh idea
daniel

I appreciate the team's transparency and honesty on this matter. Keep up the good work!

Hello Guys,

I find it weird considering that this feature is extremely complex - how come a 3rd party plugin can achieve this functionality whereas Atlassian can't?

Also, can't this be achieved somehow by enhancing the Screen Schemes module?

For instance, I would create:

• Screen A for issue View by Project Role X
• Screen B for issue View by all other project roles
• Screen C for issue Edit by Project Role X
• Screen D for issue Edit by all other project roles
• Screen E for issue Creation by Project Role X
• Screen F for issue Creation by all other project roles

Anyway, hope this will be revisited some day, because obviously it is an essential requirement in any enterprise, especially the large ones.

Best,
Pierre

Jean, entendo seu ponto de vista, mas precisamos dessa melhoria o quanto antes!

Outra coisa, o fornecedor desse plugin é imaturo e irresponsável, não responde e-mail e não libera o aquisição de licença trial para testes durante 30 dias...

Estamos precisando de uma solução definitiva urgente. Por favor, priorize essa questão dentro do time de desenvolvimento da Atlassian.

Grato.

Hello,
Is there finally hope to solve a long awaited feature?
Hiding "time tracking fields" in Jira for external users is a major request for many Jira users.

I see that a new plugin has been made available for the download instance: https://marketplace.atlassian.com/plugins/com.gebsun.plugins.jira.hidetimetracking .

This ability has been requested for more than 10 years ago (check the history of related issues to time tracking). Jira (Atlassian) came up with, for sure, many great features but never solved the real need.

I'm convinced, if this plugin works as described, this would be appreciated by many many Jira users.

Looking forward to the quick responsiveness of Jira Team to make this plugin available in "on demand".

Cheers

The fact that a number of commercial plug-ins exists proves two assertions:

1. This is a useful features that customers of JIRA want
2. It is technically possible to implement it, even though in 2003 and 2007 the architect had reasons to not implement it.

So my opinion is that it's worth having this ticket re-opened and this decision reassessed.

There is more than 1 plugin working around the lack of this functionality.
But none of them works for JIRA OnDemand. So OnDemand customers are once again stuck with no viable solution.

Ranman, Andrew - Atlassian have resolved this as "won't fix".

Ranman - That's why there's no updates, there's no point, it's not going to get done.

Andrew - have a look at Quisapps field security plugin. If that won't work for you, then I'd suggest starting looking for a replacement now. A closed-won't-fix issue is not going to get done (and even if it's re-evaluated, it won't happen in a year or so)

I'm banking on this being properly architected/implemented in JIRA in the next year or so. Failing that, I'm planning on searching for replacements/alternatives.

Any update on this in the past 2 years? It's kind of an important change. I'm hoping your "JIRA Architect" has realized that.

matthias.jupe This is basically just global. But of course you could have either several fields or several groups. Or both.

Hi David, sounds great.
Can I manage this hide fields only global or separately for every own projects?

guys, if anyone is still looking for a solution: we described a pretty low level (i.e. soft-hiding, on the client side) approach to this issue here. Please feel free to look onto this and come back at me in any case of questions.

Disclaimer: this solution requires a small plugin of which we are the developers. Better be honest upfront

This thread is so long and hard-won with deep feelings that I'm very reluctant to add anything BUT one thought I've had for anyone looking to impl JIRA that feels they cannot due to this missing feature would be to create 'shadow issues' (subtasks would be easiest) that have a security level set accordingly such that people who can see the main issue cannot see what's in the shadow issue. You'd need functionality that automates the security level setting, and functionality that automates workflow'ing the 'shadow issue' - items which should not be considered non-trivial - and there are some serious scalability costs to this approach which would need to be noodled over first. However, well, that's the sum total of constructive commentary I believe I have within me to contribute to this issue.
-wc

One more frustrated user !!!

I've also considered having a listener that resets field values to their previous values if the user is not authorized to change them.

Perhaps this could be implemented in stages, offering a set of securable fields that have a new access model. At least it would be in the core and people could build on these fundamentally secure fields. Later on other fields could potentially be migrated into the securable field system.

We've also recently come up with another work-around that involves auditing field changes instead of preventing them. Using the groovy runner we add a script field that returns the user that last edited the field. Here's some sample code if others are interested.

		def changeHistoryManager = com.atlassian.jira.component.ComponentAccessor.changeHistoryManager;
		def userManager = com.atlassian.jira.component.ComponentAccessor.userManager;

		def updateTime = issue.getCreated();
		def updaterKey = null

		def changeHistories = changeHistoryManager.getAllChangeItems(issue);
		for (changeHistory in changeHistories)
		{
			if (changeHistory.created.after(updateTime) && changeHistory.field == fieldName)
			{
				updaterKey = changeHistory.userKey;
				updateTime = changeHistory.created;
			}
		}
                
		// If there were no changes to the field, check if the field was set when the issue was created.
		if (updaterKey == null)
		{
			def customFieldManager = com.atlassian.jira.component.ComponentAccessor.customFieldManager;
			def field = customFieldManager.getCustomFieldObjectByName(fieldName)
			def value = issue.getCustomFieldValue(field)
			if (value != null)
			{
				updaterKey = issue.reporterId; //key
			}
		}

		return userManager.getUserByNameEvenWhenUnknown(updaterKey);

This is an absolute MUST HAVE feature for ANY issue tracking tool that claims to support workflow. Workflows support process, by restricting various transitions. Workflow should also support various field level restrictions. Some example: only the Assignee can change field x. Only the QA Team can edit various QA fields. Field y can only be changed in states a, b, and c.

When this feature is finally implemented, please make these restrictions transparent. Developers/Users should be able to quickly see what actions are available to them and what actions they are restricted from. For example, an uneditable field on the "View Issue" screen should be disabled/greyed out. Help should be easily available to help users understand WHY the action is unavailable. A tooltip, or nearby help icon, should explain, "The 'X' field is only editable by the QA team.".

The edit vs. view screen workaround is hard to administer, and is confusing to users. Relying on a third-party plugin to add what is essentially core functionality for an issue tracker seems like a very risky move, both for JIRA upgrades and for integration with other plugins. JIRA itself has created custom "read only fields", like the "Imported Bugzilla ID" field. We could create a duplicate read/write permissions-enabled field for every custom field type, but then we run the risk of incompatibilities/out of sync errors whenever the real underlying field changes. Additionally, system level fields remain out of reach for protecting.

I understand this is probably only necessary for "larger companies" with more involved processes, etc. But it seems like this is where you would get most of your revenue. And it seems like a very effective ad campaign to say that we support large company x, y, and z, as well as having those company members continue to use/spread your tools to other companies, small start-ups, etc. Why disqualify yourself early? Please give this feature another shot. Regards, Andrew.

You may want to watch the Live Fields features of JJupin that among others enables you to hide fields depending on any logic (custom field value, status, complex algorithms - like permissions computation for specific users, groups or roles, etc). See examples on Supported fields page or Recipe on hiding Time tracking Information.

If you have specific requirements we may be able to provide you a more targeted solution or hint.

HTH

Although this was a feature requested for some projects (one I hoping could be implemented for our internal clients), I fully appreciate the reasons for not implementing it, and really appreciate the honest and straight forward response. ANd with all the great features seen in the recent releases of JIRA I must agree it was the right decision.

Cheers!

@guis:
I think it's better to ask this on http://answers.atlassian.com

Hello,

How to create a non-editable fields?

Guillaume

Alex

yes you are right about second point. I checked again and timetracking column are visible but empty - its ok.

I have edited my previous comment.

Radoslaw,

We know about the issue with queries and are working to fix that in the next major release. As for Excel, this view is handled by JFS and the user can not view any time tracking data in Excel export if he does not have a permission. If you have any troubles with that view please e-mail me directly and we'll try to resolve it.

Alex
http://quisapps.com

Quisapps Field Security Plugin DOESN'T work properly because:

• each user can use timetracking fields on advanced queries in Jira
• each user can export to xls all fields - including timetracking fields (Menu Issues/Views/Excel) - EDIT 2012.05.04 - xls view works properly. My mistake.

So it is NOT a good solution.

@Brett Ryan - regardless as to your companies policies the pricing structure around JIRA and 3rd party plugins are orders of magnitude below the cost of All other Issue Tracking solutions in the marketplace today. If you compare JIRA with ClearQuest the maintenance fees alone would cover the entire Atlassian suite, let alone the costs involved with supporting that monster.

I understand that every Company's financial situation is different but typically when I give people a chart showing how much time their employees waste w/o the presence of a plugin it just sells itself as the cheaper option...and in JIRA's case the much cheaper option.

bah...I told myself to not get into this one...total can of worms. However, $800 for writing a commercial plugin and supporting it across multiple versions of JIRA is an odd price point to get bothered by. For most consultants and administrators supporting JIRA that's less than one days wages, at least their billable wages.

Best of luck.

@brett.ryan I also wish some of the plugins were standard functionality. But I can imagine why Atlassian would want to encourage a wider ecosystem to provide them. It's tough to make a living just by selling plugins though.

mdoar, I appreciate the work that plugin authors put in to create plugins, though I have to say that due to many of the pricing structures surrounding them it does make it hard for many of us to convince our management to purchase licenses for plugins, especially when management only see the added functionality as something that should have been present in the first place.

As an example, our management will only entertain a plugin if both the plugin benefits the business as a whole; and that the plugin is priced fairly to benefit the business as a whole.

In a situation where JIRA is used as a service centre implementation then most plugins only affect those managing the system, not those using the system.

Expensive? Compared to a $10 starter license, maybe. Compared with enterprise license costs, not really.

Please tell me this isn't off the planning board permanently. Couldn't Atlassian come up with a plugin? Quisapps was able to make a plugin - which I would grab in a heartbeat if it wasn't so bloody expensive. ($800??)

You'd have to ask Jamie over on the Behaviours plugin pages

Matt, is it possible to control Field level security (for specific roles) by using Behavior plugin? I don't think it is possible in role level!