[Jenkins-infra] Creating Sprints in Jenkins Jira
ml at beckweb.net
Fri Jun 30 14:48:19 UTC 2017
> On 29. Jun 2017, at 10:21, Catalin Luta <luta.catalin at gmail.com> wrote:
> I'm one of the contributors to the JiraTestResultPublisher plugin and I have a question related to how we should organize our development.
> Since we receive our issues in the Jenkins Jira, I thought it would be easier and straight forward to create our sprints there. This way we could stay on schedule and we'd have transparency for the users (for example, they could see planned release dates).
> But as it turns out, I can only create boards, not sprints. Since the plugins are basically components in the JENKINS project, a user requires admin rights to the project in order to create sprints. My question is: Is this implemented by design? Are we expected to handle our planning outside of the main JIRA? If so, can you recommend a solution that would allow us to link the JIRA items with some external planning?
This hasn't really come up before, probably since we've long been on a much older release of Jira and sprints are a fairly recent addition.
I'm only aware of Blue Ocean (and to a limited extent the security team) using this functionality so far.
I think I created and started sprints for Blue Ocean in the early days, and I'm willing to do this for you as well. Of course, this doesn't scale, so if it catches on with others, we'll need an alternative, but I'd be surprised if that happened. Most maintainers probably make do with a prioritized board or similar, and release when it makes sense.
More information about the Jenkins-infra