-
Suggestion
-
Resolution: Obsolete
-
None
-
None
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Background
JIRA does not natively support the idea of field level security (JRA-1330), the most popular of which is the ability to the hide Time Tracking fields from customers (JRA-2364). We know that a lot of customers really want a way for JIRA to solve this kind of problem.
View Ports
Internally at Atlassian we have been throwing around the idea of what we call "View Ports". The idea behind this is that admins can configure an alternative view of the JIRA View Issue screen for different groups. One of the items that can be configured is the ability to choose what fields are shown in the View Port.
Example Scenario
You have a company that specialises in custom development solutions and have 10 internal staff members with 200 external customers. You want to manage all your issues in one JIRA project but you do not want to expose the time tracking fields to your customers.
View Port Solution
1. Admin creates a JIRA group for all the 'external customers'.
2. Admin then creates a View Port for this group only.
3. Admin configures the View Port to show all fields except time tracking.
When anyone in the 'external customers' group logs into a specific url, they are taken to this View Port. They will not be able to login into the normal JIRA system.
Comments Please
We'd love to get your feedback in this solution and if it would work for your company.
- has a derivative of
-
- Closed
- is related to
-
- Closed
[JRACLOUD-27613] Alternative JIRA Views
Today another user asked for this feature. They want to use JIRA but want different teams to see different fields.
Just for you to know.
@Atlassian
No matter what we use JIRA for, there are almost always two parties involved. Service provider and service consumer (or customer). When there is more than one party, there will always be some information that needs to be hid from customer. Service Desk is a solution that solves only a small portion of this problem. The need to hide some fields from some users in the conventional JIRA interface is critical.
The initial idea of viewports was a promising one yet you decided not to implement it. Believe me guys, Service Desk can not meet those needs. You say it is very hard to implement this feature since it would require large portions of JIRA to be rewritten. You know what: You should start immediately!!!
JIRA is moving to an upper league these days. We, as a partner, are positioning JIRA for all kinds of needs: Request management, project & portfolio management, service desk, audits, etc... you name it. Believe me when I say this feature is needed desparately. This is more important than Service Desk or Portfolio. There is no version of future that JIRA can go on without this feature forever. Sooner or later you will have to implement this. The sooner it is done the less damage. (We are currently implementing a very large scale Atlassian project and we suffered a lot because of this. I can not put enough emphasis on how important this is.)
Hello guys,
The mentioned Hide Time Tracking plugin is now a mature product and time tracking information is not visible in JIRA UI (for users without 'work on issues' permission).
In case of any problems you can raise an issue at https://gebsun.atlassian.net/browse/HTT
Regards,
Gebsun
@Alexander: Many thanks for the info. It's indeed possible that this plugin is still early stage and that it does not yet cover all aspects.
In fact, this type of plugin was expected to be developed by Atlassian (Jira) in order to provide a solution for "hiding time tracking fields". It's a pity this has to be performed by a third party.
@Jean-Jacques I would advise you against using this new plugin at all in its current state. It just seems to work, but actually everything is still visible in change history, activity streams etc etc.
@Ronald, we're indeed in the same boat and facing exactly the same situation.
Let's hope that Atlassian (Jira) will surprise us by quickly enabling this long awaited plugin. Just want to stay positive after all.
We're in the same boat. There's a lot of things we like about Jira and we haven't found a replacement.
The need to hide time tracking doesn't affect all our projects so for the moment we're putting up with the missing functionality.
@Ronald Vallenduuk...thanks for your reply.
You indeed pointed out the different options and we looked/tried all of them.
Leaving Jira behind is indeed an option, all the others are not. But I must also say, on a positive note, we've a lot of satisfaction with other Jira features and Jira in general with Confluence, Bit Bucket and so on. But this "hide time tracking fields" is indeed the cause of lots of frustration on our side. Did you find another solution?
@Jean-Jacques Courtens: Thank you. I will check out the plugin. Hope it will fit our needs.
Jean-Jacques, I wouldn't count on it. They've been coming up with excuses for 10 years; that should tell you how much they value this feature.
You have a few options:
- Switch from ondemand to onpremise and get a plugin. Of course this comes with all the headache and cost that made you go for ondemand in the first place, so not an option.
- Double-book keeping; create two versions of each project, one internal and one external. Lots of extra admin overhead so no real option.
- Don't let customers in Jira. They will have less visibility and your team will have to copy all their comments from email to Jira. No real option.
- That leaves... find another solution and leave Jira behind.
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
Hi Edwin, thanks for the answer regarding the Field Security Plugin, but once again, it seems that Atlassian is ignoring On-Demand customers who are paying several thousands of dollars per year, but still miss a critical functionality which is being able to hide time tracking. As long as we don't have this feature, we cannot work with our customers in JIRA or JIRA Agile, which is, by the way, the exact opposite of how we need to work in Agile... The customer must be part of the team.
So, how can we work with your product then??
Anders, Normand, Peter, Bernhard, Jean-Jacques, Patrick,
Thanks for your comments. I can appreciate that you may be disappointed the closure of this issue. Making decisions like these are always difficult for us, and definitely not a part of the job that we enjoy. If we had an infinite amount of capacity, we would love to do every feature request in this tracker. However, the reality is that we are always constrained to balance the different competing priorities of the product.
At this stage, we are closing this issue because we cannot see that this issue will resolved in our foreseeable future given other priorities. We believe being up front and clear about this is a better embodiment of our values than to keep this request open.
As for workarounds to hide time tracking information, there is the Field Security Plugin developed by Quisapps available in the marketplace that can hide time tracking information (and custom fields).
Edwin Wong
JIRA Service Desk Product Manager
Resolution Obsolete? Obsolete = "no longer produced or used; out of date." Nice try. Feels a little more like Won't Fix which is a completely inappropriate way to respond to years of feedback regarding the usefulness of this feature. This is extremely discouraging and while I don't think it's a trivial development effort, I don't think it would be that difficult to implement. A little less time trying to monetize this opportunity by developing new products and little more time worrying that you're going to lose market share to a provider that understand the value of this feature.
Like Jean-Jacques, I'm a long time Jira user. I don't want to move off the platform but there's a lot of pressure to provide our customers with direct access to our PM tool (less time tracking).
You've received a lot of very specific feedback over the years in regards to this topic. Please don't make us feel like we're wasting our breath... Check out this set of Values I found from a company that would never respond as you have: https://www.atlassian.com/company/about/values
I can't agree more with the previous comments and share the disappointment. We're also building software in SaaS and we perfectly understand technical difficulties. But we also know that there is always a technical solution. In my honest opinion, hiding the time tracking fields (in views, history, API...) is not as complex as you are expressing it. It's I believe a very important feature when willing to use Jira as a collaboration tool with people outside your organization (customers, consultants...).
This issue is open since more than 10 years, it's not that you couldn't take this request into account in all the enhancement you performed on Jira since then.
Don't get me wrong, we still believe Jira is a great tool with some nice enhancements. If we are insisting and angry, is because we don't want to change our jira environment. But make no mistake, if we encounter a tool with the minimum requirements including hiding the time tracking features...we will change!
I understand that atlassian want's to push Service Desk and for most people this will solve the problem with time time tracking fields, but not for me.
In my project setup our customers can look into our agile boards. external developers work on our boards and can view jira tasks.
That means they all see the timetracking fields an the time booked. We use Tempo, Jira Agile and Service Desk.
But I do not see Service Desk as a solution for hiding time tracking fields. We use the Jira Field Security Plugin for that purpose, but this plugin patches Jira which is not very nice. We rather would like a softer way of doing that.
Peter
added a comment - So the solution to my JIRA problem is to buy a different product? How is that a resolution? With Service Desk, we have to spend hardware resources on it, train an admin, train users and customers all in the sake of not actually fixing the original problem. This is NOT resolved as this was in my mind a large deficiency with JIRA. I need field level security in my issue tracking tool, I don't use JIRA as a service desk and trying to shoehorn my issue tracking into Service Desk is not an option just for field level security
Peter
added a comment - So the solution to my JIRA problem is to buy a different product? How is that a resolution? With Service Desk, we have to spend hardware resources on it, train an admin, train users and customers all in the sake of not actually fixing the original problem. This is NOT resolved as this was in my mind a large deficiency with JIRA. I need field level security in my issue tracking tool, I don't use JIRA as a service desk and trying to shoehorn my issue tracking into Service Desk is not an option just for field level security Edwin, I understand that you addressed the "Viewports" issue with JIRA Service Desk, but for Time Tracking, if JRA-2364 is closed, what is the alternative for us? How can we hide everything related to time tracking from customers having access to a project?
Can you explain a little bit what is the plan from Atlassian to address this problem?
Thanks, Normand
Anders Ingestedt
added a comment - I just must say that this makes me sad. We have been waiting for a solution to JRA-2364 for a looooong time and two years back Atlassian pointed to this issue instead. To now read that you plan to never ever solve it is discouraging to say the least. JIRA will thereby never be a complete solution for projects where customers are involved. I understand that there are technical difficulties, but I thought you had skills enough to manage also complex problems within Atlassian.
Anders Ingestedt
added a comment - I just must say that this makes me sad. We have been waiting for a solution to JRA-2364 for a looooong time and two years back Atlassian pointed to this issue instead. To now read that you plan to never ever solve it is discouraging to say the least. JIRA will thereby never be a complete solution for projects where customers are involved. I understand that there are technical difficulties, but I thought you had skills enough to manage also complex problems within Atlassian. "Viewports" was a concept we explored that could provide the ability for admins to partition the view of a ticket into "end users" and "insiders". The intention was to allow admins to tailor an interface to JIRA that encourages end users to create, view and collaborate on requests, while your internal teams take advantage of the full power of JIRA to process these issues. We had hoped that this solution would also help customers who wanted to hide time tracking fields as per JRA-2364 (Hide Time Tracking estimates from certain users).
Your feedback on Viewport and the specific needs for hiding time tracking made it clear that generic Viewport wasn't the best way to solve customers' problems. There were two very different use cases:
1) Using JIRA to power their service desk operations. This idea evolved into JIRA Service Desk.
2) Hiding time tracking fields (usually because external consultants or customers were collaborating in JIRA, but everything except time tracking information)
Service Desk:
One of the key parts of JIRA Service Desk is the Customer Portal, which implements much of the original concepts of Viewport, but tailored for the service desk use case. Using the Customer Portal you can build customer / end-user oriented views of issue types - you can hide fields, rename fields, re-map workflow statuses. You can effectively give a different view of your issue to different audiences. With the recent release of JIRA Service Desk 1.2, you can also lock out your Customer Portal users from being able to log in to JIRA altogether.
If you've been waiting for "Viewports", I recommend you give JIRA Service Desk a try. Service Desk is much more than what Viewport started out as - there are queues, reports, service level agreements, knowledge base integration and much more in development.
At this stage, we will close off this issue, as we will unlikely revisit shipping "Viewports" as originally described in this issue. Thank you to everyone who has contributed to this issue.
Time Tracking:
A deeper look into time tracking with customers and their use cases revealed that just hiding the standard JIRA time tracking fields from the UI would not be enough. They needed to be inaccessible through REST APIs, change history, and a number of other areas. There were other fields that customers needed hidden that were "related" to time tracking. So a simple solution of hiding time tracking from View Issue would still be expensive to develop, add more complexity to JIRA, and not actually solve the full problem. Due to this, at this time we are leaving JRA-2364 closed.
Edwin Wong
JIRA Service Desk Product Manager
Ronald, why do you think nothing happened? JIRA Service Desk got created for a start. Atlassian, a status update on this one would be very useful
This thing is unbelievable. The original request goes back 11 years. Then this ticket was created 2 years ago and still nothing happens.
How on earth can you ignore a top 10 customer request for more than a decade?
Gonna have to start looking for an alternative solution.
The only option I've come across sofar in all these threads is double bookkeeping but unless there is a way to automate it that's no viable solution. It would just add too much overhead for the team.
I add my voice to this one. Being able to hide time tracking from customers is a MUST HAVE, even 2 years later...
2 years gone. This idea is still nowhere. In the meantime, time tracking fields still cannot be hidden from "external" users. Why is the suggestion of Thorbjorn not implemented completely eludes me.
yes Thorbjorn. It really is that simple an I also hope, that they will implement some group- or user-bound permissions for time-tracking.
Thorbjørn Sigberg
added a comment - Why not simply add a permission under "Time tracking permissions" in the permission scheme that says "View time tracking information", and if you don't have this permission, the time tracking control is not loaded or is void of information when viewing an issue?
Thorbjørn Sigberg
added a comment - Why not simply add a permission under "Time tracking permissions" in the permission scheme that says "View time tracking information", and if you don't have this permission, the time tracking control is not loaded or is void of information when viewing an issue? 
Luiz Felipe
added a comment - É importante a implementação dessas melhorias. Isto ajudaria o gerenciamento dos administradores JIRA.
Quando ficará pronta?
Luiz Felipe
added a comment - É importante a implementação dessas melhorias. Isto ajudaria o gerenciamento dos administradores JIRA.
Quando ficará pronta? Check my comment on https://blogs.atlassian.com/2013/11/insight-jira-service-desks-pricing-model/#comment-122275 and please vote and add any additional comments here: JSD-201
This is exactly what a customer of ours needs right now. The fact that their customers can see all the Time Tracking information, is not something that is acceptable. Right now I am looking into a workaround, but hiding the Activity Stream gadget is not possible for a certain group. The only possible thing seems to disable it, for everyone.
Fernando Claros
added a comment - I'd love to see this feature.
On a different note, I'm not sure if it would resolve our particular situation:
We don't want some of our users (external QA, mainly) to see our versions (our Project Road Map), but there is no way to keep the road map working and restrict its visibility to some allowed users (or exclude some others).
Would that feature help us with this problem?
Fernando Claros
added a comment - I'd love to see this feature.
On a different note, I'm not sure if it would resolve our particular situation:
We don't want some of our users (external QA, mainly) to see our versions (our Project Road Map), but there is no way to keep the road map working and restrict its visibility to some allowed users (or exclude some others).
Would that feature help us with this problem? We're on the same boat. We do let clients in but don't want them to see all time estimations.
Anders Ingestedt
added a comment - We have the same problem as Niklas. We are letting the customers in to JIRA, but we do not like to share the time spent information. View Ports does not seem to solve this problem in a good way. I would much rather see the original problem of field level security solved.
Anders Ingestedt
added a comment - We have the same problem as Niklas. We are letting the customers in to JIRA, but we do not like to share the time spent information. View Ports does not seem to solve this problem in a good way. I would much rather see the original problem of field level security solved. 
Niklas Gotting
added a comment - Hiding field using plug or Javascript is not an option! 
This is not secure enough, since neither Issue Navigator nor XML-view or export hides it.
I mean we sell solutions and peace of mind based on value vs. charging hours...
We want transparency in general, but not in all aspects!
Niklas Gotting
added a comment - Hiding field using plug or Javascript is not an option!
This is not secure enough, since neither Issue Navigator nor XML-view or export hides it.
I mean we sell solutions and peace of mind based on value vs. charging hours...
We want transparency in general, but not in all aspects! 
Normand Carbonneau
added a comment - David, it is not allowed for On-Demand users... niklas.cambio, rmazurkiewicz and al other only wanting to hide a field: You could 'soft-hide' a field (in the UI) using the CUTE for JIRA Plugin. This is only based on Javasript and hides the field in the UI, not in XML-view or export. But this would be enough for most of you I guess. You could also implement a check to hide the field only for users that a part of a specific gourp (in LDAP/JIRA internal) if you whish to.
We are working on a how to for this case I might post a link here soon...
Edit: currently this addon is only allowed for download users, no On-Demonad.
Radosław Mazurkiewicz
added a comment - AGREE - We all need is to be able to hide those f... time tracking fields. Nothing more, nothing less. JRA-2364
Add permissions for those 3 little fields is too complex???
Radosław Mazurkiewicz
added a comment - AGREE - We all need is to be able to hide those f... time tracking fields. Nothing more, nothing less. JRA-2364
Add permissions for those 3 little fields is too complex???
For our Company, transparency with Customers is a key component. For that reason our setup have been to use one Project the whole way from Bug issue, through Solution issue, followed by a Delivery issue. However with today's limitation that Time tracking including both estimated hours and real hours can't be protected from Customer viewing, we must separate Solution issues in a separate project.
Bummer
Niklas Gotting
added a comment - - edited For our Company, transparency with Customers is a key component. For that reason our setup have been to use one Project the whole way from Bug issue, through Solution issue, followed by a Delivery issue. However with today's limitation that Time tracking including both estimated hours and real hours can't be protected from Customer viewing, we must separate Solution issues in a separate project.
Bummer Oh f*** yes! This feature (or the old Field level security) would make my life as a JIRA admin sooooo much easier. +1 form me, hope to see this feature soon!
I Agree @Bernard, Atlassian has quite some impressive tools and for sure a lot of customers.
But as shared a lot of times, this issue is open since more than 10 years (at least the original issue). Atlassian is for sure working out a fantastic feature but what I currently need (and I know for sure, lot's of customers too) is to be able to hide those f... time tracking fields.
Hiding time tracking fields was the original request, nothing more, nothing less.
We all understand development complexities, priorities and so on...
But common...10 years, jira agile as @Normand Carbonneau is saying...we're far from it!!!
I'm following this issue since more than 2 years now...I had a little hope in Jully 2013...and today...we simply don't know what, how, when.
I believe this is my major concern with Jira!! and in the end maybe a deal breaker.
Bernhard Grünewaldt
added a comment - Customer collaboration over contract negotiation ^^
But we all know how hard it is to implement every feature the customer wishes for. And atlassian has a loooot of customers ^^
Bernhard Grünewaldt
added a comment - Customer collaboration over contract negotiation ^^
But we all know how hard it is to implement every feature the customer wishes for. And atlassian has a loooot of customers ^^ No news from Atlassian for all that time... And they call it JIRA Agile 
.
Hey Atlassian, please read the Agile and SCRUM definitions... Remember, Deliver often by small increments, etc...
Daily Users: 200 - 240 (50% of it only rarely)
Active Users: 1.000
Issues: 45.000 (~17.000 per year)
Projects: 120
But the problem was due to large dashboards fewer users.
Bernhard Grünewaldt
added a comment - @Marcel:
I have a hosted version with a 500 User license. And actual 400 users in use together with approximately 60 projects.
We just did a first installation test on our dev-system and will test the plugin in detail the next weeks on the production system.
And I really need to hide Time Tracking fields, because of our companies data privacy statements ...
@Max: Thx for the hint with the performance. I will also look into that. How many users/projects did you have in your installation?
Bernhard Grünewaldt
added a comment - @Marcel:
I have a hosted version with a 500 User license. And actual 400 users in use together with approximately 60 projects.
We just did a first installation test on our dev-system and will test the plugin in detail the next weeks on the production system.
And I really need to hide Time Tracking fields, because of our companies data privacy statements ...
@Max: Thx for the hint with the performance. I will also look into that. How many users/projects did you have in your installation? Anders Ingestedt
added a comment - @Marcel Lange:
Note that the original issue (JRA-1330) was reported in 2003, so do not expect anything soon...
Anders Ingestedt
added a comment - @Marcel Lange:
Note that the original issue ( JRA-1330 ) was reported in 2003, so do not expect anything soon... We also had the Field Security Plugin in use. Unfortunately we had to remove that with an increasing number of users, because JIRA was no more accessable several times a day. This is due to a bug in the plug-in related with large dashboards. Also with us was suffering the JIRA performance because the plugin does not spread the work across multiple CPUs. We therefore hope that Atlassian will soon offer a proper solution.
@Bernhard Grünewaldt: Big THX for the plugin hint. I'll give it a try. Do you have the hosted version of jira or do you run the application on your own mashine?
@Marcel Lange:
good luck to have an expected date...Atlassian is screwing up to deliver this feature in appropriated time and especially on his lack of being able to hide time tracking fields
Bernhard Grünewaldt
added a comment - @Marcel,
I am also waiting for this. We decided at our company to use this plugin until Jira provides a built in solution:
https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfs
It costs some money. But it works fine with my Jira 5.2.4 installation.
@Atlassian: Please provide information about the releasedate of Viewport Plugin, thx.
https://www.atlassian.com/viewport
Bernhard Grünewaldt
added a comment - @Marcel,
I am also waiting for this. We decided at our company to use this plugin until Jira provides a built in solution:
https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfs
It costs some money. But it works fine with my Jira 5.2.4 installation.
@Atlassian: Please provide information about the releasedate of Viewport Plugin, thx.
https://www.atlassian.com/viewport We need this feature very fast in our hosted solution! Are there any timings for that Feature?
Alena Zhytnytska
added a comment - @Atlassian
Seriously, guys, we really need this feature...how long we have to wait?
Alena Zhytnytska
added a comment - @Atlassian
Seriously, guys, we really need this feature...how long we have to wait? I mean this issue was created mar/12 and the movie was announced Jul/13.
So the movie production takes 1year+
@Atlassian - where is the software ???
Agree with Jean-Jacques!
And Atlassian are creating tools to manage development with Agile/SCRUM methodologies
Multiple, small and incremental deliveries to have constant feedback from the customers... Do you remember Atlassian?
I just hope we won't have a huge new application that is great, but that is not addressing our real initial needs...
@Radek Mazurkiewicz, the issue regarding "hiding time tracking fields" is almost open since 10 years!
View Port would normally solve this.
In the end, View port could be a great enhancement with lots of enhancements. As user I have the feeling that we will receive a R&R (Rolls Royce) where initially we expected much sooner to have a simple Lada to hide the time tracking fields as most of the information could be public to our customers. 
We had to wait one year to watch nice movie on https://www.atlassian.com/viewport
@Jira: any news regarding delivery date of this long awaited feature (hiding time tracking fields)?
Is it still for this century?
Sorry to be ironic...but this issue has such an old history....
Highly interested in this solution! We'd immediately try it out if there was a version..
Any info on a possible release date?
As seen in JRA-33804 the ability of any reporter to enter an "Original Estimate" remains a problem for us. When designing our JIRA system the documentation led us to believe that the visibility of Original Estimate on Create Issue screen was controlled by the Work on Issues permissions. Atlassian's response to this was to change the documentation rather than address the underlying need, leaving us with an awkward deployment of our system.
It would be good if this new Viewport design is able to address this need. To restate; we want global read access to the time-tracking values, but visibility and editability on the Create Issue screen should be limited to specific roles.
To be truly honest though, a much simpler solution would be to add an "Estimate Issues" permission.
Bernhard Grünewaldt
added a comment - Is there any date for the release of Viewport Plugin? 
Jon Verville
added a comment - atlassian.com/viewport
I need this desperately! I don't think all users need to see time tracking.