Community
Participate
Working Groups
Red Hat uses custom statuses for bugs. Instead of UNCONFIRMED, NEW, ASSIGNED, REOPENED, RESOLVED, VERIFIED, CLOSED, the Red Hat bugzilla instance has NEW, ASSIGNED, MODIFIED, ON_DEV, ON_QA, VERIFIED, RELEASE_PENDING, POST, CLOSED. I see how the mylyn UI maps the standard, non-customized statuses. However, that does not work for the custom statuses above. It looks like the TaskAttribute keyed by "bug_status" has an options() method. I can see custom statuses there, but in the UI nothing related to that shows up. It would be good if a "Status" CChombo would get rendered (showing whatever statuses have been configured by the BZ instance) in the UI if the Bugzilla connector is used. This would allow to change the status of a bug to things like "ON_QA", etc. Thanks!
Have you tried the custom workflow support implemented as part of bug 259291 and described here: http://wiki.eclipse.org/Mylyn/Bugzilla_Connector#Custom_Transitions ?
(In reply to comment #1) > Have you tried the custom workflow support implemented as part of bug 259291 > and described here: > http://wiki.eclipse.org/Mylyn/Bugzilla_Connector#Custom_Transitions ? Yes. The above document seems only be concerned about transitions logic. In other words which transitions should Mylyn allow and which not when trying to submit. I can add a transitions mapping file, but that doesn't change the UI of individual Bugzilla bugs. How would I change status to ON_QA for instance? I might be reading the code wrong, but it looks like the CustomTransitionManager class and related code does not introduce UI for showing, let alone, changing custom statuses. Thoughts? Thanks!
Created attachment 187781 [details] Custom_Workflow_and_StatusTransition.txt Here an example that use custom status transitions for the Mylyn test repo. So I think it should work for you.
(In reply to comment #3) > Created attachment 187781 [details] > Custom_Workflow_and_StatusTransition.txt > > Here an example that use custom status transitions for the Mylyn test repo. > > So I think it should work for you. Thanks Frank! Using this transition file did the trick (using a weekly build). You can close this bug if you like. Remark: There is certainly room for improvement in terms of documentation. E.g. I was unaware that "name" in the transition file is a keyword. I can try to make the documentation on the wiki better if you wish.
(In reply to comment #4) > (In reply to comment #3) > > Created attachment 187781 [details] [details] > > Custom_Workflow_and_StatusTransition.txt > > > > Here an example that use custom status transitions for the Mylyn test repo. > > > > So I think it should work for you. > > Thanks Frank! Using this transition file did the trick (using a weekly build). > You can close this bug if you like. > > Remark: There is certainly room for improvement in terms of documentation. E.g. > I was unaware that "name" in the transition file is a keyword. I can try to > make the documentation on the wiki better if you wish. It would be great if you find time to do the documentation.
