[Jenkins-infra] JIRA project for Blue Ocean
jdumay at cloudbees.com
Mon Apr 17 23:28:28 UTC 2017
As a subproject composed of a lot of different moving pieces, I believe it
would be beneficial to split the blueocean-plugin component from the
JENKINS project in JIRA to a new project called BLUEOCEAN.
The main reason here is that as a subproject we maintain our own very
separate release and development lifecycle from Jenkins core and JIRA’s
projects capability offers a number of benefits that could help the team
manage the project better:
- We would like to use JIRA features, such as version tracking, to
manage the lifecycle of our releases. We’ve had users re-opening tickets
because they had seen them closed as fixed but they had not been released.
- Track different components of Blue Ocean (there are quite a few now)
using components, rather than abusing epics for this purpose (see our
- Reduce namespace pollution for sprints. Daniel Beck has asked me to
prefix sprint names with “Blue Ocean” to avoid collisions.
- JIRA treats projects in a first class way in its UI and it will be
easier for users to find where to add their tickets.
- Added bonus here is that we could use JIRA Issue collectors
inside the UI of Blue Ocean to request features or report bugs, without it
spamming the JENKINS Jira project.
I would propose that Michael Neale and I both be administrators of the new
JIRA project. We would adopt the exact same JIRA workflow as JENKINS. We
spend the majority of our day in the Jenkins JIRA today and maintenance
would not go neglected.
What do you think?
Director of Product Management.
Skype: jdumaycb Twitter: i386
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Jenkins-infra