jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven 2.x Changes Plugin
  • Maven 2.x Changes Plugin
  • MCHANGES-92

JIRA Report Improvements

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta-3
  • Fix Version/s: 2.0
  • Component/s: jira
  • Labels:
    None
  • Patch Submitted:
    Yes
  • Number of attachments :
    2

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.

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    maven-changes-jira-report-improvements.patch
    07/Jan/08 6:21 PM
    16 kB
    Niall Pemberton
  2. Text File
    MCHANGES-92-jira-column-configuration.patch
    12/Jan/08 9:11 PM
    8 kB
    Niall Pemberton

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Dennis Lundberg added a comment - 08/Jan/08 5:33 PM

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 - 08/Jan/08 5:33 PM 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
Permalink
Niall Pemberton added a comment - 12/Jan/08 9:11 PM

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 - 12/Jan/08 9:11 PM 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
Hide
Permalink
Dennis Lundberg added a comment - 13/Jan/08 11:22 AM

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 - 13/Jan/08 11:22 AM 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.
Hide
Permalink
Niall Pemberton added a comment - 13/Jan/08 9:36 PM

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 - 13/Jan/08 9:36 PM Thanks Dennis - I tried it out and it all looks good to me. Unfortunately you applying these changes has encouraged me to submit more

People

  • Assignee:
    Dennis Lundberg
    Reporter:
    Niall Pemberton
Vote (0)
Watch (0)

Dates

  • Created:
    07/Jan/08 6:21 PM
    Updated:
    13/Jan/08 9:36 PM
    Resolved:
    13/Jan/08 11:22 AM
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.