[jbosstools-issues] [JBoss JIRA] (JBTIS-648) Improve the tracking of BPMN2 issues

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13188704#comment-13188704 ] 

Max Rydahl Andersen commented on JBTIS-648:
-------------------------------------------

You cannot move the BPMN project to jboss tools - it is an eclipse.org project. 

We've done various approaches:

a) have duplicate jira with link to the relevant bugzilla(s)
b) grant QE access to triage bugs in bugzilla (see https://wiki.eclipse.org/Bug_Reporting_FAQ#Bug_Editing_and_Triage)
c) latest we've created the ERT project that import eclipse issues with the rht keyword and allow us to triage on our side as well as have the bugzilla alive.

Sounds to me that B would work for BPMN and that you should make sure your issues in bugzilla are cleared marked what version they are fixed in ? 

I personally avoid any use of red hat bugzilla since dealing with one jira and one bugzilla is enough :)


> Improve the tracking of BPMN2 issues
> ------------------------------------
>
>                 Key: JBTIS-648
>                 URL: https://issues.jboss.org/browse/JBTIS-648
>             Project: JBoss Tools Integration Stack
>          Issue Type: Task
>          Components: BPMN2
>    Affects Versions: 9.0.0.CR1
>            Reporter: Andrej Podhradsky
>            Priority: Critical
>
> Currently, BPMN2 issues are reported at Eclipse Bugzilla or Red Hat Bugzilla. Our problem is that we are no able to directly query all resolved issues related a specific build (for this purpose we use https://www.eclipse.org/bpmn2-modeler/whatsnew/).
> Unfortunately, in Eclipse bugzilla QE doesn't have permissions to change a status of issues which were not created by QE (it seems that only commiters have such permissions). This is very important in testing cycles.
> In Red Hat bugzilla all BPMN2 issues are a part of the BxMS products. I'm not sure whether this is the right place for all BPMN2 issues (it would also mean to clone existing issues from Eclipse bugzilla).
> Other solutions could be
> * Jira will be our primary tracker for BPMN2 issues (and all issues be cloned from Eclipse BZ)
> * or move the whole project to the Jira JBoss Tools
> What do you think? Do you have any ideas how to improve the process?



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)