JIRA Bamboo Integration

[Prasad Andrews]

1) In JIRA issue create/update page:

• If the ‘Affects Application(s) / Vendor(s)Required’ field is selected as ‘ESPN’ then a new custom fields ‘Release Components’ and ‘Release version’ should be displayed in below format.

Field name - text	Field name- text	Field value - dropdown
Component 1	Release version	No relese,r1,r2,r3..
Component 2	Release version	No relese,r1,r2,r3..
Component n	Release version	No relese,r1,r2,r3..

Note: Field name – ‘Components n’ – These fields are static to the ESPN application.

The field name ‘Release version’ should be populated based on the available release version for the selected component, environment and BU region in JIRA.

• Once the user creates/update issue, a post function should be triggered to capture the following fields and store it in a JIRA variable – the field is – Environment, Business Unit, affected applications, Component[1,2, n], release version.

2)In JIRA workflow:

In the SW Release (IT Operations) or in Deployment JIRA workflow, when the issue is in ‘To Deployment’ status if the RM clicked that button then the ‘In progress’ transition should trigger the post function which will trigger the customized bamboo deployment plan. If the Bamboo deployment result is a success, then the issue should be transitioned to next state ‘Deployment Completed’. If the bamboo deployment is a failure, then the issue should be transitioned back to ‘To Deployment’.

The custom Bamboo deployment plan URL is framed using the custom issue field recorded in JIRA variables.

[Prasad Andrews]

Any updates on the requirement?