On 05/03/2006, at 12:55 PM, Graham Dumpleton wrote:
Although changing the workflow to add new status values is
interesting, in reality
not sure this could be done as workflow is probably global across
all projects.
Actually, if want to get that pedantic and formalised, it does look
like one can select
an alternate workflow. The level of administration access we have
probably does
not allow us to change it, let alone see what options exist.
Anyway, digging around with the XML-RPC interface into JIRA, found
the list of
issue codes with descriptions at end of this email. You can see that
some other
project must have a customised work flow, don't know which project
though.
My purpose of playing with XML-RPC interface was to find a way of
closing off all
those 3.2.7 issues. The bulk actions mechanism in the web pages
doesn't seem
to allow a bulk closing of selected issues, only changing certain
information about
them. I'd rather not go through 60+ issues closing each one. :-(
{'id': '1', 'description': 'The issue is open and ready for the
assignee to start work on it.', 'name': 'Open', 'icon': 'http://
issues.apache.org/jira/images/icons/status_open.gif'}
{'id': '3', 'description': 'This issue is being actively worked on at
the moment by the assignee.', 'name': 'In Progress', 'icon': 'http://
issues.apache.org/jira/images/icons/status_inprogress.gif'}
{'id': '4', 'description': 'This issue was once resolved, but the
resolution was deemed incorrect. From here issues are either marked
assigned or resolved.', 'name': 'Reopened', 'icon': 'http://
issues.apache.org/jira/images/icons/status_reopened.gif'}
{'id': '5', 'description': 'A resolution has been taken, and it is
awaiting verification by reporter. From here issues are either
reopened, or are closed.', 'name': 'Resolved', 'icon': 'http://
issues.apache.org/jira/images/icons/status_resolved.gif'}
{'id': '6', 'description': 'The issue is considered finished, the
resolution is correct. Issues which are not closed can be reopened.',
'name': 'Closed', 'icon': 'http://issues.apache.org/jira/images/icons/
status_closed.gif'}
{'id': '10000', 'description': 'The issue is open but work on it is
temporarily suspended until further feedback is received determining
its resolution.', 'name': 'On Hold', 'icon': 'http://
issues.apache.org/jira/images/icons/status_needinfo.gif'}
{'id': '10001', 'description': 'The issue was on hold, and feedback
was received indicating that further action are required towards its
resolution.', 'name': 'Continued', 'icon': 'http://issues.apache.org/
jira/images/icons/status_generic.gif'}
{'id': '10002', 'description': 'A patch for this issue has been
uploaded to JIRA by a contributor.', 'name': 'Patch Available',
'icon': 'http://issues.apache.org/jira/images/icons/
status_document.gif'}
{'id': '10003', 'description': 'A patch attached to this issue has
been reviewed by another contributor.', 'name': 'Patch Reviewed',
'icon': 'http://issues.apache.org/jira/images/icons/status_visible.gif'}
{'id': '10004', 'description': 'A patch attached to this issue has
been revised by the contributor.', 'name': 'Patch Revised', 'icon':
'http://issues.apache.org/jira/images/icons/status_information.gif'}
{'id': '10005', 'description': 'A patch attached to this issue is
ready to be committed.', 'name': 'Patch Finalized', 'icon': 'http://
issues.apache.org/jira/images/icons/status_up.gif'}
