- edited description
Timesheet gadget - Summary for group doesn't show all users
Issue #791
wontfix
In the old gadget if I configure the timesheet gadget to show a group it shows all users. The new version only shows users who have logged time. One thing I use that view for is specifically to see who hasn't logged time yet. In the old report that's obvious: a user with an empty row. In the new report I need to read down and compare the report with the list of users in the group. That's made even harder by the fact that the users are in random order.
Comments (9)
-
reporter
-
- changed status to open
-
reporter
The 'All Users' option requested in
#786is a completely different feature (and implemented badly if you ask me). The request in#786is to include all users who have logged time, whether they are in the selected group or not. What I'm asking for here is to include all users in the selected group, whether they have logged time or not. Like the old gadget does. -
As you might have seen, I've reopened it back.
Why do you think it's implemented badly, since you mentioned?
-
- changed status to wontfix
Hi Ronald,
It does not look possible - underlying REST api getUsersFromGroup requires at least admin privileges.
Note, for P2 it was enough to have BROWSE_USERS permission. But it appeared as limitation, users that had now Browse Users permission could not see Group timesheet, while now it is possible.
So, please consider it as design decision, feature made differently, hopefully for good.
Thank you.
-
Account Deleted
I definitely need this feature back. Is there a workaround?
Just as knowing who has logged time, I need to know who hasn't.
-
Sorry, no.
-
Account Deleted
I am using the 2.9.5.2 version with Jira Server 6.3.9 and admin privileges. From the documentation that you cite, Is this a problem only on Jira 7+ with the updated API? Is there a previous version I can rollback to where this feature works with the Jira setup that I have?
-
Hi Vincent,
Sorry for confusion, this problem is applicable for JIRA Cloud only. For JIRA Server there should not be such problem.
Thank you.
- Log in to comment