|
[
Permalink
| « Hide
]
Ken Warkentyne added a comment - 13/Nov/03 07:23 PM
If this feature is going to be added, could it be generalized to control the visibility of other fields (including custom fields) for specific groups of users?
I propose to have a specific permission to view the work log as well as any actual times. This would be internal (dev team) information only.
The time estimates on the other hand I consider information for the issue originator, helping him decide whether it's worth doing. Hi,
I agree that it is worthwhile the customer being able to view the estimate, but it makes no sense that they can edit the estimate. Surely only somebody with 'Work on issues' permission should be able to enter/edit the estimates? The current behaviour in this particular area seems like a bug to me... Cheers, Mike Until this improvement is implemented, a workaround is to add <webwork:if> tags around JSP blocks displaying time tracking info (or edit links).
Eg, in viewissue.jsp, around line 31: <webwork:if test="remoteUser/groups/contains('jira-developers') == true"> The places that we need to hide this appear to be:
Any others that I have missed? I don't think that you missed anything. I've just tried to write in more details where time tracking fields and estimates should be hidden.
======================================================================== When work is logged, "Work Logged" emails is send. It is already possible to control who should receive these via the Work Logged On Issue notification event. But JIRA should also look to see if the user has Time Tracking permissions. ======================================================================== ======================================================================== The "Work Log" should also be hidden. The "Change History" and "All" should have some kind of filter not displaying time tracking changes. ======================================================================== ======================================================================== Btw: The temporary solution with editing the .jsp and .vm files to manually filter out time tracking for certain users did not help.
By editing .jsp and .vm files I found that it was almost possible to hide Time Tracking from certain users. The only two places I could not hide them was: The Issue Navigator (when displaying the 3 time tracking columns) and the when viewing an issue (notes in the "All" and "Change History" pages). Second it should be mentioned that if the user not allowed to see the time tracking estimates where a bit of a hacker it would not be a problem for him to view for example the Work Log reports (because I only was hiding the links to the reports - not the reports themselves). I think this is an important point, if customers have access to JIRA. Perhaps you could tie it to
the "Work On Issues" Permission. For example you could simply add to the viewIssue.jsp <webwork:if test="@fieldVisibility/fieldHidden(., 'timetracking', ../string('type')) == false && hasIssuePermission('work', /issue) == true"> I know have to change it in many more jsps like tabs.jsp and so on.(limit the tabs to comment tab as you can see time tracking fields in all tabs except for "comment").Preset Reports and many more... Also everywhere where This all could easily be achieved but where I have to change the source code? I would try implement it for our company, as it is an important point for us. Thanks, Philip Philip,
I haven't investigated, but if you could reuse the 'Work on issues' – To hide the time estimates I really do not want to hack my installation and to modify that many templates and files. Any news on this item? Is Atlassian waiting for field level security to solve this issue or can this be done in parallel as improvement to the timetracking feature? Especially because some users report they almost have finished it, why can't you take that back into the product, as it deals mostly with template stuff?
> Is Atlassian waiting for field level security to solve this issue
Exactly right. We think that we should tackle this once and for all. I am not sure who has finished implementing this, however, in the past we have had some rough experiences integrating contributed code. Most often it is written in the most 'direct way' to get the job done, so it might not work for other customers and is difficult to maintain and support. Anton the last comment is of 28 oct 06, is it known whether this is going to be build in or not. At this moment we have the same need of this there we do not want our external customers see how much work we have on issues etc.....
We need this feature too. Sometimes it is necessary to hide all the worklog information from customers. At the moment some has to manage two separate JIRA projects, one for customer interaction, one for internal issue management and time tracking.
Now with the improved Worklog features in JIRA 3.10, showing that Atlassian got the importance of the Time Tracking Feature, i am wondering what happens to this Feature Request behind the curtain? Any news on this feature?
Regards Another vote for this feature! We do not want to disclose all time tracking information to our customers. Neither would we want our customer to enter an original estimate for any bug s/he reports.
Now that call
 ) are waiting for the possibility to hide the time tracking fields from their customers....
please take this serious it's a key item to use this product or not! I couldn't agree more. This would be a great feature for us. I would just add a couple of more levels of permissions:
Estimates:
Worklog/Time Spent:
In a simple scenario we would have two groups: Team and Clients. Clients could see their own estimates / worklogs / actual hours spent on a task but they would not be able to see our internal teams entries. I don't want clients to have detailed access to an individuals time per task, etc... Team members could see each other's worklogs. Patrick,
As of 3.10 you are now able to set permissions on who can edit worklogs (own and other's). Cheers, We are thinking about switching to Jira, but this one issue does realy hurt us. Some of our Customers may see the estimate, but never they should see the whole information. You know, some times you ar faster than estimate, some times you are slower - we do not want to discuss this for every issue.
When can we expect a final solution? Someting new about this ?
This is the most required feature for us to use JIRA with our customers ... We strongly need this feature, any chance it will go in soon?
It's unbelivable that this has not been solved so far. We now have to implement this feature because we REALLY NEED it. So we have to hack all the pages to do this.
Why isn't there anyone listning at Atlassian? This is really a MUST HAVE feature and letting customers do all this ugly hacking with all the update trroubles is really bad style! I'm really angry about this.... Max Max
You took the words out of my mouth This is a huge deal for some of our customers and hacking jsp and vm is no fun we're so tired of waiting for this and hacking every release of JIRA to make this work. Maintenance headaches for what seems like a minor fix or a feature.
Atlassian, what does it take to get this done?!!! It's been years already! Hi there,
me too I think that this is a must-have feature. Right now I have to be careful during development of a project, or customers can see estimates and work done on features and it's really bad style. It would be great to get it fixed, also because I don't fancy hacking JIRA and make my life a nightmare when it will be time to upgrade... Thanks, Max this feature request is unassigned, I'm not sure if anyone at Atlassian actually sees our complaints...
Well, I talked with some people in Atlassian via email, they suggested me that the best way to get it resolved was to vote and comment on the issue.
Even if it's unassigned, I spotted some people from Atlassian in this thread, so they're likely to receive email notifications for new comments Max For now i am assembling together the changes need to be done
Does anyone managed to do the hack in the issue Navigator? Agreed, for us this is also a MUST HAVE feature. We were alraedy very dissapointed that
Trying to make every field configurable in this way would be a major overhaul to the system. Are we all willing to wait 12-18 months and no new features? I am not. If they can make Estimate and Time Tracking configurable, that would be "more then good enough" for me. I think some want the customers to see the estimate and others don't. So make all time tracking one configuration point, won't do the job. We would be OK with our customers seeing the estimate, but not the actual time spent.
Oh what a pity! Since upgrading Jira and enabling the time estimation and tracking in the last week I was so happy to have such a great tool ... but ...
As mentioned above: I cannot show the details of the time tracking information to our customers! So I cannot use this feature! Hi,
Thank you for voting and commenting on this feature, we do receive notifications with your comments and pay attention to them. As some of you have mentioned in your comments, this feature touches a lot of places in the system: view pages, reports, issue navigator, notifications, numerous edit/update operations and many others. Therefore, we will need to allocate a fair bit of time to add this feature. If we do allocate this time, other improvements would have to wait. Based on the feedback that we have, there are a number of other improvements that are more popular than this one, and therefore we will look at implementing them first. Due to this we do not have an implementation date for this feature. Cheers, Hallo Anton, you said:
> As some of you have mentioned in your comments, this feature touches a lot of places in the system: So you expect all your customers to allocate this "fair bit of time" by themself? What kind of stupid math is this??? And what ist this "fair bit of time" you are talking about in hours? Based on your (Atlassians) own recommendation to be found on If you at Atlassian do it with a little more planning and a bit more "clean" work than we did, I guess it will cost you at max So I really, really can't understand what stops you from implementing this long missing and very importeant feature. If Atlassian is this short on ressources, maybe it was the wrong decision to choose Jira as a strategic product for supporting our SW Development .... Max I think this feature would have been fixed years ago it Atlassian provided JIRA with a Free software license, under which they're using the components from Apache Foundation. Most software companies tend to choose dual licensing these days realizing the value of community support and contribution.
Following all the comments above, and glad that other people are still active on this. This is definitely a must have feature. Considering the number of SW development houses that use JIRA I am suprised that this has not been added.
Hi folks!
I am Max Weißböck's collegue slash hacker and here is our complete approach to hiding time tracking for certain users while it is enabled for others. Our approach is not generic, it is not complete, it is not perfect and definitely improvable but it is exactly what we most desperatley needed at the moment and what was the easiest to accomplish. We decided to publish our solution to the community. But first, let me say a few angry words. This issue is open for 4 3/4 years, many people and companies hunger for a solution - for ANY solution - and all you say is "there are a number of other improvements that are more popular than this one, and therefore we will look at implementing them first"? Come on! Just tell us that you - as everyone else of us - have not the slightest idea of how to correctly solve this issue in ANY way and in proper time. Do not lie to your paying customers! Here is our solution. all you have to do is to replace the original jsps and vms with ours (in the attached HideTimeTrackingHack_by_SphinxITConsultingGmbH.rar), do what is written after "configured" in the following lines and restart jira. We defined a user group "hide-worklog-hack" which you must create in your jira. All users of that group do not receive any time tracking informations afterwards. we also use the jira greenhopper plugin. if you do not use greenhopper, you do not have to apply those changes; everything else still works the same. in the modified jsps and vms, our changes are marked with "sxhelpdesk" and "sxhelpdesk_greenhopper". note that you do not need to look at the modifed files - simply replacing the original is all you have to do. introducing Notes
modified files for restricted time tracking access:
greenhopper:
Hopefully our solution is useful for some of you! Improvments are welcome. Greetings, Patrick ,I just wanted to thank you for taking the time to assemble these instructions
I still haven't looked into it yet , but from a first look , its what i was looking for So , Thanks again Well done Thanks Patrick, this is also what I really needed.
However, I must say that the HideTimeTrackingHack_by_SphinxITConsultingGmbH.rar solution did not work for me (Jira 3.12.3-#302, Standard edition). I still see Work log data in issue details, also tabs "All" and "Work Log". I defined user what I wanted to restrict to hide-worklog-hack group. Maybe the problem could be that I am using project roles for other permissions (not groups), and the restricted user's role does not have any permission to get time tracking, also time tracking for him is disabled. But he still sees work logs. Maybe I misunderstood your guide statements like "users of hide-worklog-hack do not see any time tracking information and they only see comments, no 'all', no 'history', no 'worklog'..". Is there something extra I should do (configure?), or is it just result what should happen after updating the jsp files? In my case, this particular thing did not happen. Thanks Patrick, I have applied your patches and it hides the time-tracking bars beautifully, just what we needed to prevent external customer from seeing progress!
As we consider allowing our users to have more transparency into our development, this is also becoming an important issue. As suggested above, right now we are considering a separate project for users' bug reporting from where issues would be copied and moved to be addressed by a developer. This is clearly somewhat clumsy. Hiding time tracking from a group of users would be great functionality!
The lack of support for this five year old idea will probably mean that we won't be using JIRA at my company. Sucks.
 Folks at Atlassian:
How hard would it be to validate the hack provided here by Patrick Cemper ? We use JIRA here in our company. JIRA is a great tool, however, we are NOT renewing our maintenance until this improvement is accomplished. It seems that this is not a system-wide change, that will impact JIRA's performance and the like. Why Atlassian ignores one of the most voted issues to implement minor interface changes ? Also, as you can see, we are all HUNGRY for this issue to be solved, so why not share your problems with us ?
I am sure this issue will be easily solved after that. This would be great if it could be fixed. Otherwise i need start doing this manually. Nothing that i look forward to.
Thanks Patrick,
I did the patch
So see the comment from Patrick Cemper: http://jira.atlassian.com/browse/JRA-2364?focusedCommentId=117120&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_117120 It is based on the patch of Patrick Cemper http://jira.atlassian.com/secure/attachment/25880/HideTimeTrackingHack_by_SphinxITConsultingGmbH.rar You will find the patch-points with the marker 'sxhelpdesk'. I put the files in directories that you just need to copy them at all. The only difference from the 3.13.1 patch to the 3.13.2 patch is the only changed file atlassian-jira\WEB-INF\classes\templates\plugins\issueviews\single-xml.vm. Installation:
Usage:
Frankmartin Wiethüchter If you want to get rid of the time tracking information in your email notifications one viable solution would be to simply take that out completely from your emails.
For Jira release 3.13.2 copy the two files from the attachement to these directories. issueplugins:
issuesummary
My company has recently purchased JIRA after using confluence for awhile.
We are a software company that has many international markets that have different business practices. It is going to be a show stopper for us to not have this resolved. We are using JIRA for not only Bug tracking but as a support desk for our customers. The customers in some cases should see time tracking for invoice purposes and double checking the hours involved in certain processes. Others should not see any of the Time Tracking Reports, Work log tab, or even the time estimate. This very much seems like a permissions issue that would be easily resolved by project roles or the permissions groups. Especially if it has been hacked. Essentially the work is half done. it just needs to be integrated. Same problem for us.
It is for us a motivation not to renew our maintenance if there is not a clear message from Atlassian on this subject. Is there a possibility of an update from Atlassian on this issue?
Even if the time estimates are hidden the worklogs tab would be visible unless the permissions dictated. I just wanted to be clear on what we need. To have the time tracking portion (all of it) to be hidden from one user group and visible to others. The time tracking is intercompany and scvhedule verification and we do not want customers seeing it. Regards, Steve Shutts Hi,
I use version 3.12.2 and I have replaced the files provided by Patrick Cemper for version 3.12.1 but It doesn't works correctly on all views. This are correct: This are incorrect: I have created the group "hide-worklog-hack" and members of this only can "Browse project" and "create Issues" in permission Scheme I have been looking all .jsp and .vm and I have seen the caracter "|" between some lines and I have thougth that maybe was incorrect and I have deleted it, but I still can see issue details. I also have tested with files for version 3.12.3 but also not work. Someone knows what could be the problem? Thanks in advance, Javier Problem Resolved, the cache saved the last files and although I restarted Tomcat Time Tracking still did appear. dito to the former comments
"It is for us a motivation not to renew our maintenance if there is not a clear message from Atlassian on this subject. " Atlassian, any news on this feature? We are currently facing a SHOWSTOPPER in using Jira with one of our customers because of this.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Short Term Roadmap
Major
Hide Time Tracking estimates from certain users (e.g. customers)
