Allow issues to be displayed regardless of existing time logs

Issue #537 resolved
Former user created an issue

Helo Andriy, it's me again ;-)

We've stumbled upon another (hopefully) small topic which would result in a great improvement for time-tracking.

Right now the TimeSheet plugin Dashboard view displays only issues (for a certain user or for yourself) which were used for time logging in the past days/weeks. Even if you choose a filter only those tickets are displayed with former time-logs.

As a result you can only log work times on tickets you already worked on - not on NEW tickets even if they are part of a filter.

When using a filter it would be great to have the possibility to choose yourself wheter only tickets with time logs OR all tickets from this filter (regardless of former time logs) should be displayed. If you choose this setting, it would result in constantly the same set of tickets (as set in an certain filter) beeing displayed... and you could easily enter time logs to all of these tickets.

Comments (19)

  1. Former user Account Deleted
    • changed status to open

    Interesting. The problem using the Timesheet Configuration "In Progress Issues" setting is that it's global. You need to know,that we have several departments with douzens of JIRA projects... It becomes an inpossible task to find a JQL query suitable for all of them. I belive a local solution would be much more suitable. That's why I proposed using a filter. Every user knows best what he is working on. It might be a specific project, a specific component a specific version or even a fix set of defined tickets. What we would need is a way to allow each user to configure his gedget the way he wants to display only tickets relevant to him.

  2. Andriy Zhdanov

    Hi Sebastian,

    Regarding your original idea: when using a filter - option to show all tickets from this filter (regardless of former time logs). I worry that it may be too many issues. Gadget does not have pagination. Thus this global option to enable this feature to show only some certain issues.

    And adding 'In Progress Issues' gadget option with filter or JQL, seems redundant.

    Do all departments use similar workflow, so that you could rely on issue status to display in gagdet?

    Otherwise, did you consider using labels for this? E.g. In Progress JQL: labels in (stick_in_timesheet)

    Finally, there is super flexible trick, set In Progress JQL to e.g.: filter = "Sticky Issues for Timesheet", and then everyone can create his own filter with this name, to whatever he or she wants. If filter does not exist for a user, nothing happens. Also you can share filters with certain users or groups to simplify their lives. See also

    Please let me know if it solves your problem.

    Thank you.

  3. Former user Account Deleted

    The flexible trick ("filter = YXZ") did it - fantastic, thank you! The important thing of course was:

    If filter does not exist for a user, nothing happens.

    By creating a filter and sharing it only with my team all the other departments were not affected... that was absolutely crucial! And since I'm using a filter I can perfectly identify all tickets I want to be displayed.

  4. Former user Account Deleted
    • changed status to open

    Hello Andriy - we have a little drawback concerning this issue... probably a bug. Setting the "Progress JQL" works only for the current week/month. If you jump to the next or previous week/month using ">>" / "<<", the stated JQL seems to be ignored :-(

  5. Andriy Zhdanov

    Hi Sebastian,

    Yes, that's designed behavior, but looks like nothing prevents it from changing. I will notify you on update.

    Thank you.

  6. Former user Account Deleted

    Hi Andriy. We've been using the "in progress issues" global configuration for a month by now and it works quite well. Still it's a little bit limiting in terms of "beeing global". If you're using e.g. 3 Time Sheet gadgets in your dashboard, all 3 of them are influenced by the global setting in the same way resulting mostly in the same output. Do you see any chance for adding the "in progress issues" setting into the individual gadget configuration as well (probably overwrting the global setting if set locally) - so that each gadget can be configured differently? With this we would be able to split our one huge gadget consisting of everything into a few smaler gadgets consisting only of specific (e.g. project releated) issues. We believe this would improve gadget-overview, orientation and navigation greatly.

  7. Andriy Zhdanov

    Hi Sebastian,

    You can use Project or Filter option per gadget, if you don't need issues matching a filter to be always displayed in the gadget, regardless whether they have worklogs during the displayed period.

    Thank you.

  8. Former user Account Deleted

    You know, unfortunately that's what this entire ticket is all about => the need to always display tickets regardless of them having worklog entries :-( Hence simply using a filter doesn't help us.

    By the way - since the "in progress issues" setting is global it limits us to use only one gadget. Adding a second gadget would result in mostly the same tickets beeing displayed again (depending on the filter set in "in progress issues") in the new gadget.

    That's why I'm asking for having the option "in progress issues" localy - per gadget. The implementation does already exist (globaly) - so adding it localy shouldn't be that difficult. The only obvious problem is: what if both settings are set - local and global. My approach would be "object oriented" - hence overwriting the global setting with the local one...

    Any chance for that? Problems? Difficulties?

  9. Andriy Zhdanov

    I'm just trying not to make too many options.

    Do you think that option like Show rows with no work will help? So when using Project or Filter gadget will show all issues matching selection, regardless of them having worklog entries. This should work also with Group option, so all users in group will be shown, regardless of them having worklog entries.

    It should work in case of Group and hopefully Role, or Project or Filter options. And it will merge global 'In progress Issues' also, when it is applicable.

    But it will not have any effect in default view, i.e. for single user.

    If this sounds good, could you please create separate issue, copying your use-case above and also this suggestion?

    Thank you.

  10. Log in to comment