On 6/20/2013 12:19 PM, Richard Eckart de Castilho (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689375#comment-13689375 > ] > > Richard Eckart de Castilho commented on UIMA-3014: > -------------------------------------------------- > > Given that closed issues cannot be edited, I'd suggest that issue not be > close. At least they should not be closed until the version they are assigned > to is released. Slight clarification - they cannot be edited without first re-opening them, so in particular, bulk-editing operations are not possible.
-Marshall > >> improve jira report for releases sort order >> ------------------------------------------- >> >> Key: UIMA-3014 >> URL: https://issues.apache.org/jira/browse/UIMA-3014 >> Project: UIMA >> Issue Type: Improvement >> Components: Build, Packaging and Test >> Reporter: Marshall Schor >> Assignee: Marshall Schor >> Priority: Minor >> Fix For: parent-pom-5 >> >> >> Our current practice sometimes "closes" issues, othertimes "resolves" them. >> This distinction is not significant in how we operate. But it's sorted >> ahead of the issue number, making it harder to locate a particular issue. >> Drop this sort key. Then we'll have a sort order of issue type (e.g. bug, >> improvement...) and within each of those a list sorted by issue number. The >> next column will indicate the closed or resolved status. > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira >
