Upgrade of JIRA & Planning Alerts workflow changes
Matthew Landauer
Just to let you know - I've upgraded our bug & ticketing system JIRA
to version 4.0. It's got a bunch of usability improvements and a
generally cleaner look.
Please let me know if you spot any problems with this new version. I
haven't managed to get the git plugin for this version of JIRA working
yet unfortunately, but other than that it should all be there.
Also, I've made a workflow change to the Planning Alerts project. If
it works and people like it I'll make the same change on the other
projects in due course.
As you're probably aware a ticket in JIRA by default has a number of states:
Open
In Progress
Resolved
Closed
Reopened
The important ones are: Open, Resolved and Closed
The difference between Resolved and Closed has always been confusing
to most people. So, the first thing I've done is to remove "Resolved".
So things can go straight from Open to Closed. Simple, huh?
Now onto the next change I made:
When you make a change to the code and commit it to your own
repository and want it merged in to the main code and deployed on the
site, you would comment on the ticket and maybe set the ticket to
resolved.
This situation occurs so often and isn't clearly handled in our system
that it makes sense to add another state to a ticket "Merge Required"
which basically says "Hey, this ticket is basically done, but needs to
be merged into the main repository - when that's done and only then is
the ticket closed"
So, now when you write some code which you want merged in for the
Planning Alerts project just set the status to "Merge Required".
Thanks!
Matthew