The issues on Time Sheet gadget has no link

Issue #659 resolved
Former user created an issue

This is a copy of a suggestion request originally reported on jira.atlassian.com under this link: https://jira.atlassian.com/browse/JRA-44525. Please check there for the details of the request.

Comments (17)

  1. Andriy Zhdanov

    Hi Bartek,

    Thank you for drawing my attention.

    Hi Lawrence,

    Unfortunately, it's not possible to add link there because this is group of the issues with the same summary. But you can click Details link, and see all issues with corresponding value of the field in the report.

    Additionally, I may suggest to make report break down issues by selected field. Please let me know if you'd find it useful.

    Thank you.

  2. Lawrence Lachman

    Hello Andriy,

    What do you mean that it's not possible to add the link because this is a group of issues with the same summary? Do you mean because they are all subtasks to a parent task, and they all share the same summary of the parent task? Because all of the subtasks have their own unique summary.

    I did click on the Details link, and that clearly does have links to the corresponding JIRA issues. Thank you.

    I don't understand your last suggestion. What steps do I need to follow to make a report break down issues by selected field?

    Thank you,

    Lawrence

  3. Andriy Zhdanov

    Hi Lawrence,

    Yes, your understanding is correct. I just thought about grouping, I thought you use Group By: Summary. If you do, try not doing this. Summing sub tasks should be sufficient and it will have the link!

    Last thing is not possible yet. I think I can implement it, but it will need some significant work, so I can't promise to be available soon. But looks like you don't need it. Please let me know otherwise.

    Thank you.

  4. Lawrence Lachman

    I do use Group by Summary. If I don't use it, then I cannot see every JIRA issue that time is logged to. The output is the same regardless of whether I sum subtasks. Really, I don't know how this got to be this complicated, but my request is so very simple:

    By grouping by summary, I see each JIRA issue that my developers worked on for the week. However, the summary is just a single sentence, without the identifying JIRA issue number (e.g., CG-5). So I have no idea what the JIRA issue number is, and the summary is not inherently a hyperlink to the issue, so there's no way to easily navigate to that issue. So I either want to have the JIRA issue displayed along with the summary, and/or have the summary be a hyperlink to the issue. That's all I want. I have no desire to create reports, or do anything else fancy with this gadget. To me, these are such basic, fundamental requests that make the gadget useful, I cannot imagine why it's been this difficult to find a way to do that.

  5. Andriy Zhdanov

    You're absolutely right, this is simple basic scenario, until you use Group By Summary, it is overcomplicated! Please do not use this, and let me know what is not working then.

  6. Lawrence Lachman

    If I don't use Group By Summary, there is no way to identify the individual JIRA issues that each developer logged to during the week. I've tried not using it. It doesn't work.

    With it set to Group By Summary, and Summary for group(s) jira-developers and filter Emma Bowman, I see 12 different JIRA issues that Emma - and only Emma - worked on this week.

    The minute I set to Group By to None, then I see the four developers in the jira-developers group, and just daily totals for each one. There is no breakdown of what they worked on, and the gadget is no longer limited to just Emma, it now displays four developers.

    Ugh.

  7. Andriy Zhdanov

    I see. You've found a good workaround, beside it does not show issues.

    Well, you need to click Details link to see issues broke down by users in selected groups, also if not using Group By: Summary.

    Alternatively, you may try instead of specifying Groups, add condition to the Emma Bowman filter, like assignee in membersOf("jira-developers") or worklogAuthor in membersOf("jira-developers"), but of course it's not all the same.

    Sorry I can't suggest anything else.

    The workaround using Group By: Summary does not allow to show issue, because it is expected to be a group of issues.

  8. Andriy Zhdanov

    Hi Lawrence,

    Version 2.9.1 with the feature to break down grouped issues. Now you should be able to use Group by: Worked User, and with Show Details: Yes, you should see individual issues that group members worked on.

    Please let me know how it works.

    Thank you.

  9. Lawrence Lachman

    Andriy, Thanks for letting me know. How do I ensure I am working with v2.9.1?

    Here is what I see in the About JIRA message:

    License Information for JIRA

    JIRA v6.5-OD-08-001

    Copyright © 2002 - 2015 Atlassian Corporation Pty Ltd.

    The use of this product is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

    This product includes software developed by the Apache Software Foundation.

    This product also includes the following libraries which are covered by the GNU LGPL license: •atlassian-image-consumer (com.atlassian.image:atlassian-image-consumer:jar:1.0.1) •carol (carol:carol:jar:1.5.2) •carol-properties (carol:carol-properties:jar:1.5.2) •Core - API (net.sourceforge.jwebunit:jwebunit-core:jar:3.2) •CSS Parser (net.sourceforge.cssparser:cssparser:jar:0.9.5) •CSS Parser (net.sourceforge.cssparser:cssparser:jar:0.9.9) •datafile (datafile:datafile:jar:1.3.3) •dbUnit Extension (org.dbunit:dbunit:jar:2.5.0) •HtmlUnit Plugin (net.sourceforge.jwebunit:jwebunit-htmlunit-plugin:jar:3.2) •image4j (org.jclarion:image4j:jar:0.7) •Java Native Access Platform (net.java.dev.jna:platform:jar:3.4.0) •Java Native Access (net.java.dev.jna:jna:jar:3.4.0) •JCaptcha (com.octo.captcha:jcaptcha-api:jar:2.0-alpha-1) •JCaptcha (com.octo.captcha:jcaptcha:jar:2.0-alpha-1) •jcommon (jfree:jcommon:jar:1.0.8) •jfreechart (jfree:jfreechart:jar:1.0.13) •JSCalendar (1.0) •jStyleParser (net.sf.cssbox:jstyleparser:jar:1.16-atlassian-1) •Streaming API for XML (javax.xml.stream:stax-api:jar:1.0-2) •xapool (xapool:xapool:jar:1.3.1)

    This product also includes code written by other third parties.

    Additional details regarding these and other third party code included in this product, including applicable copyright, legal and licensing notices, are available in the "licenses" directory under the JIRA installation directory.

    License Information for JIRA Plugins

    JIRA Portfolio v1.10.3-OD-001-D20150720T123754

    Copyright © 2014 Atlassian Corporation Pty Ltd.

    The use of this product is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

    This plugin includes software developed by the Apache Software Foundation.

    This plugin includes the following libraries covered by the GNU LGPL license: •GNU Trove(net.sf.trove4j:trove4j:3.0.3) •JGraphT - Core(org.jgrapht:jgrapht-core:0.9.0) •jStyleParser(net.sf.cssbox:jstyleparser:1.16-atlassian-1)

    This plugin also includes code written by other third parties.

    Additional details regarding these and other third party code included in this plugin, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.

    JIRA Capture v2.9.1.113

    Copyright © 2002 - 2013 Atlassian Corporation Pty Ltd.

    The use of this plugin is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

    This plugin includes software developed by the Apache Software Foundation.

    This plugin also includes code written by other third parties.

    Additional details regarding these and other third party code included in this plugin, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.

    JIRA Agile v6.7.10-D20150729T044856

    Copyright © 2002 - 2013 Atlassian Corporation Pty Ltd.

    The use of this plugin is subject to the terms of the Atlassian End User Agreement, unless other specified therein.

    This plugin includes software developed by the Apache Software Foundation.

    This plugin also includes code written by other third parties.

    Additional details regarding these and other third party code included in this plugin, including applicable copyright, legal and licensing notices, are available in the "licenses" directory inside the plugin.

  10. Andriy Zhdanov

    Hi Lawrence,

    Sorry for delay. I need to request separately an update in JIRA Cloud, but I still need to figure out few things before this. I'll update you on progress, not later than by the end of next week, but update itself will need some more time, may be another month.

    Thank you.

  11. Lawrence Lachman

    Andriy,

    I accidentally stumbled onto a way to provide the links to the various line items on the timesheets I am creating. I have to set the filter to point to one of my team members, and then group by Assignee. While this works well, and does indeed show links and the correct times, it does not show the times that my employees log to issues that are not assigned to them. For example, if Mary helps Bill troubleshoot an issue for two hours, and then she logs two hours onto a task assigned to him, then that time does not show up on my timesheet for Mary. I really just want all time that is logged by Mary for that week to show up, so I realize that the Group By setting is not correct, but if I leave it set to None, then the gadget just shows the line totals for every member of my team, not the individual issues that one of them worked on.

    I'm sure that there is a configuration setting I'm just missing to make this work correctly. Would you please let me know what that is?

    Thanks,

    Lawrence

  12. Andriy Zhdanov

    Hi Lawrence,

    I believe you should use Group by: Worked User, and refine filter - it should point to team member(s) using worklogAuthor clause, instead of assignee, e.g. worklogAuthor in membersOf("jira-developers").

    Thank you.

  13. Log in to comment