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

[Andrej Podhradsky (JIRA)]

     [ https://issues.jboss.org/browse/JBTIS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrej Podhradsky closed JBTIS-648.
-----------------------------------


I'm closing this issue since QE has all needed permissions.

> 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: 4.0.0
>            Reporter: Andrej Podhradsky
>            Assignee: Robert (Bob) Brodt
>            Priority: Critical
>             Fix For: 4.3.0.Final
>
>
> 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)