We are evaluating Jira. At present we are stuck on how to use Jira to solve the challenge how to control issues raised against individual versioned services, of which ultimately we could have many. We note that Jira only supports versioning at project level (ref. 1) and not at a component level. This in turn impacts how an issue is tracked against many projects - effectively the issue would have to be cloned.
I have looked through API documentation hoping to be able to programmatically create a Jira project through an API, perhaps after a Jenkins build but this does not seem possible through your new REST API (ref 2).
As far as we can tell the Jira plugins for Jenkins and SVN (our build tool and repository) also do not have the functionality to programmatically help create/manage Jira projects.
What am I missing? There must be a way to use Jira to track issues against high volumes of services each with versioned components. For example component ABC version 2.3 of service XYZ has a bug. How do we track this without significant manual Jira management?
References:
https://jira.atlassian.com/browse/JRA-3501
http://forums.atlassian.com/thread.jspa?threadID=53119, http://docs.atlassian.com/jira/REST/latest/
Thanks,
JC
JIRA Command Line Interface createProject action or the underlying SOAP API for same.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.