Detected release version is mandatory in Spira Team 4.2.0.1

Wednesday, July 1, 2015
Avatar
Hello

I am using SpiraTeam 4.2.0.1 with JIRA 6.3.15.

I am noticing that "Detected Release" is a mandatory field for an incident in SpiraTeam v4.2.0.1 as a result of which JIRA isnt recognising the version of the release.
I can successfully bring in new bugs that I created on JIRA into Spira Team; however a new Incident/Bug from Spira Team isnt being passed over to JIRA because of the "Detected Release".

I also note that the new incidents that were created in SpiraTeam as a result of synchronization from JIRA have the "Detected Release" field empty which is fine; but just wondering when this is a "Mandatory Field" in SpiraTeam how is the synchronization overriding this?

I am mainly interested in the integration to work from SpiraTeam to JIRA.
Also note that "Detected Release" isn't a mandatory field in SpiraTeam 4.1.0.5, so is this something that was intentionally done on 4.2 update. 
Please let me know if there is a way to disable this or whether this is hard coded?

Any help would be much appreciated, thanks.

Thanks




1 Replies
Monday, July 13, 2015
Avatar
re: praveens84 Wednesday, July 1, 2015

Hi Praveen

You should be able to make the field optional in the Administration > Edit Workflows section. However if you are logging the incident from executing a test, it will automatically inherit the release from the test run. In that case you should just map the release to the corresponding version in JIRA (unless it doesn't exist in JIRA, in which case the data sync will automatically create it for you).

Regards

Adam

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Wednesday, July 1, 2015
  • Last Reply: Monday, July 13, 2015
  • Replies: 1
  • Views: 15849