Issue Details (XML | Word | Printable)

Key: MDLSITE-706
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Eloy Lafuente (stronk7)
Reporter: Eloy Lafuente (stronk7)
Votes: 0
Watchers: 2
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Moodle.org Sites

Create two new fileds "Affected Branches" and "Fixedfor Branches"

Created: 03/Apr/09 06:22 AM   Updated: 25/Apr/09 10:49 PM
Return to search
Component/s: tracker.moodle.org

File Attachments: 1. Java Archive File MoodleBranchesCustomFields-1.0.1.jar (6 kB)


Participants: Eloy Lafuente (stronk7), Martin Dougiamas and Michael Blake
Security Level: None
QA Assignee: Martin Dougiamas
Resolved date: 25/Apr/09


 Description  « Hide
Right now we have a lot of filters (searches) based in the "Affected versions" and "Fixfor versions". While that's nice it's a bit heavy to edit all those filters each time we release new Moodle versions.

Analyse the possibility and implement two new custom fields that will group those versions into well know moodle branches, surely by getting the two first integer in the versions so:

1.9.1 ==> MOODLE_19_STABLE
1.9.2 ==> MOODLE_19_STABLE
2.0.1 ==> MOODLE_20_STABLE
a.b ==> null

Ciao :-)

PD: I'll install them in test tracker soon. Just polishing them a bit. ;-)

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Eloy Lafuente (stronk7) added a comment - 03/Apr/09 06:22 AM
Must support multiple branches, be indexed and searchable, obviously.

Eloy Lafuente (stronk7) added a comment - 03/Apr/09 07:50 AM
Wow, pretty easy (once you get the whole Maven2 dev environment properly installed).

Attached there is one standard JIRA plugin containing two custom fields:

  • Moodle Affected Branches: Shows the branches affected by one issue, given their affected versions.
  • Moodle Fixed Branches: Shows the branches fixed for one issue, given their fixfor versions

Both are displayed in the Issue page and are searchable, so all filters can be switched from using versions to branches.

They are installed in test tracker right now, plz, play with them.

To install it in production:

  • Copy it to /home/jira/jira/edit-webapp/WEB-INF/lib
  • build.sh
  • copy /home/jira/ROOT.xml to /usr/local/tomcat/conf/Catalina/localhost/
  • JIRA will be autodeployed in 1-2 mins.
  • Go to Administration -> Custom Fields and add them.
  • Got to Administration -> Indexing and rebuild indexes (10mins aprox).


Eloy Lafuente (stronk7) added a comment - 03/Apr/09 08:25 AM
The whole Maven project in now in CVS:

http://cvs.moodle.org/contrib/tools/jira/moodle_branches_customfields/

GPL, of course


Michael Blake added a comment - 03/Apr/09 04:43 PM
nice addition eloy!

Eloy Lafuente (stronk7) added a comment - 03/Apr/09 06:13 PM
One +1 (MD/Michael) required to install this in prod tracker and upgrade all filters to use them.

Ciao


Eloy Lafuente (stronk7) added a comment - 17/Apr/09 02:31 AM
Should I install this in production? And upgrade filters to use them?

Martin Dougiamas added a comment - 17/Apr/09 10:33 AM
Oh cool!

Yes please +1!


Eloy Lafuente (stronk7) added a comment - 24/Apr/09 05:29 PM
Scheduled for this weekend. JK informed about downtime. Ciao

Eloy Lafuente (stronk7) added a comment - 25/Apr/09 09:22 AM
Installed in production + indexes rebuilt. Going to edit all the "filter manager" filters to use the new fields. Ciao

Offtopic: I had some problems upgrading, JK, because the ROOT.xml file in /home/jira (the one that is copied to tomcat) was pointing to old (3.13.2) jira database). I've fixed them (the prod and test ones).


Eloy Lafuente (stronk7) added a comment - 25/Apr/09 10:49 PM
Done. All filters have been updated to use the new "branches" custom fields. resolving as fixed, ciao