Thread | Jira synchronizer: one to many projects mapping?

Adam S

re: Filip Baert on Thursday, December 13, 2012
Friday, December 14, 2012

Hi Filip

No, I'm afraid this is not supported, each JIRA project needs to be mapped 1 to 1 to a SpiraTeam project.

Regards

Adam

Filip Baert

re: Adam S on Friday, December 14, 2012
Friday, December 14, 2012

ok, too bad.

I will write some synchronizer myself.

Any suggestions?
I was thinking about following workflow:
- user fails a test, a spirateam ticket is entered
- in the mean time, user creates a JIRA ticket (not automatically done)
- user fills in JIRA id in spirateam ticket in a custom prop

a poller uses the soap of both applications to:
- read the jira ids from spirateam
- get the latest info from jira for this ticket
- updates the spirateam ticket with this info

in that way, we see up to date info in spirateam of all our relevant tickets.

Or I could even take it a step further where the user enters a spirateam ticket and enters a JIRA project code in some custom field.
A poller can then check via the soap if there are tickets with a jira project code but no jira ticket id.
If this is the case, a Jira ticket could be created in the jira project mentioned.

could be an improvement for your jira synchronizer?
you only have to add the freedom to enter a jira project code during ticket creation and the synchronization of multiple projects.

Filip

Name:
Body:
Tags:

Name:
Body: