|
History
| Log In
|
|
|
|
[
Permlink
| « Hide
]
Ken Warkentyne - 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? 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 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Hide Time Tracking estimates from certain users (e.g. customers)
