Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-beta-3
    • Fix Version/s: 2.0
    • Component/s: jira
    • Labels:
      None
    • Flags:
      Patch

      Description

      OK heres my wish-list to improve the JIRA report:

      • Be able to configure which columns are shown on the report
      • Make the following additional columns available on the report: Reporter, Type, Priority, Version, Fix Version and Component
      • Be able to configure the "Fix Version" to show on the report (rather than all versions)
      • Be able to configure which "types" are shown on the report (rather than all types)
      • Currently the configurable Status, Resolution and Priority values are ignored (because of bugs in the url parameters used)

      I realize the Fix Version and Types can be configured using the existing "filter" - but thats not a very user friendly feature.

      Attaching a patch which does all of the above.

        Activity

        Niall Pemberton created issue -
        Hide
        Dennis Lundberg added a comment -

        I have partially applied your patch with modifications. Thanks!

        Bullets 1 and 2 have not been applied yet. I need more time to look at that part of the patch.

        Bullets 3 and 4 have been applied.

        Bullet 5 was solved by MCHANGES-89.

        Show
        Dennis Lundberg added a comment - I have partially applied your patch with modifications. Thanks! Bullets 1 and 2 have not been applied yet. I need more time to look at that part of the patch. Bullets 3 and 4 have been applied. Bullet 5 was solved by MCHANGES-89 .
        Hide
        Niall Pemberton added a comment -

        Thanks Dennis, seems you have partially applied the fix for 1 and 2 (changes to JiraXML and JiraIssue to harvest the additional columns) would be really good to be able to 1) Configure which columns are shown and 2) specify the order in which they are rendered, which is what the rest of the patch does. I tested this out quite a bit with Commons IO and I think it really makes the report more useable.

        I've refreshed with your changes and am attaching a new patch with the remainder for 1 and 2 - in case it makes your life easier, and more likely yo apply - its slightly different (I moved one line from JiraMojo to JiraReportGenerator). If theres anything about it you don't like, let me know and I'll try to fix/re-submit a new patch.

        tia

        Niall

        Show
        Niall Pemberton added a comment - Thanks Dennis, seems you have partially applied the fix for 1 and 2 (changes to JiraXML and JiraIssue to harvest the additional columns) would be really good to be able to 1) Configure which columns are shown and 2) specify the order in which they are rendered, which is what the rest of the patch does. I tested this out quite a bit with Commons IO and I think it really makes the report more useable. I've refreshed with your changes and am attaching a new patch with the remainder for 1 and 2 - in case it makes your life easier, and more likely yo apply - its slightly different (I moved one line from JiraMojo to JiraReportGenerator). If theres anything about it you don't like, let me know and I'll try to fix/re-submit a new patch. tia Niall
        Niall Pemberton made changes -
        Field Original Value New Value
        Attachment MCHANGES-92-jira-column-configuration.patch [ 31817 ]
        Hide
        Dennis Lundberg added a comment -

        The new patch was really helpful and saved me some time, thanks!

        I have applied the second patch with modifications. Most notably I moved the default-value from JiraReportGenerator to JiraMojo. The reason is that default-values for parameters in a mojo are automatically included in the documentation.

        A new 2.0-beta-4-SNAPSHOT has been deployed.

        Show
        Dennis Lundberg added a comment - The new patch was really helpful and saved me some time, thanks! I have applied the second patch with modifications. Most notably I moved the default-value from JiraReportGenerator to JiraMojo. The reason is that default-values for parameters in a mojo are automatically included in the documentation. A new 2.0-beta-4-SNAPSHOT has been deployed.
        Dennis Lundberg made changes -
        Assignee Dennis Lundberg [ dennislundberg ]
        Status Open [ 1 ] Closed [ 6 ]
        Resolution Fixed [ 1 ]
        Fix Version/s 2.0-beta-4 [ 13722 ]
        Hide
        Niall Pemberton added a comment -

        Thanks Dennis - I tried it out and it all looks good to me. Unfortunately you applying these changes has encouraged me to submit more

        Show
        Niall Pemberton added a comment - Thanks Dennis - I tried it out and it all looks good to me. Unfortunately you applying these changes has encouraged me to submit more
        Mark Thomas made changes -
        Project Import Sun Apr 05 09:14:45 UTC 2015 [ 1428225285377 ]
        Mark Thomas made changes -
        Workflow jira [ 12717927 ] Default workflow, editable Closed status [ 12749464 ]
        Mark Thomas made changes -
        Patch Submitted Yes [ 10763 ]
        Flags Patch [ 10430 ]
        Mark Thomas made changes -
        Project Import Sun Apr 05 22:40:15 UTC 2015 [ 1428273615853 ]
        Mark Thomas made changes -
        Workflow jira [ 12955592 ] Default workflow, editable Closed status [ 12992926 ]
        Mark Thomas made changes -
        Assignee dennislundberg [ dennislundberg ] Dennis Lundberg [ dennisl@apache.org ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Closed Closed
        5d 17h 1m 1 Dennis Lundberg 13/Jan/08 11:22

          People

          • Assignee:
            Dennis Lundberg
            Reporter:
            Niall Pemberton
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development