Introduction

Never worked with Jira before? No problem. Please first read the Jira training Basics page.
This chapter is part of is part Jira training for Information Systems, below the Jira setup for Information Systems - Change Advisory Board (CAB)  is explained.

Change Advisory Board (CAB)

Change advisory Board (CAB) project is used for approval of fixes and creation of a functional/technical conceptional design document.

CAB Issue types

One of the two following conditions must be met to create a CAB issue.

1. Bug: Bugfix to deliver a functional/technical solution for the original SD issue. SD issue remains open until the fix has been applied.
2. Story: Non-bugfix for internal improvement, prevent (recurring) issues for the future. SD issue can be closed, user will be informed that current issue is fixed but there will still be worked on in the background to prevent from happening again or improvements.

Under the SD issue the reporter and requested participants can be informed about the change applied/ to be applied but is also used to collect information from the requester.

CAB Workflow

CAB issue creation

Change advisory Board issues can be created via a SD-issue that have status IN PROGRESS.

1. Add a comment with specific information for requesting CAB.
2. Use button Workflow and select Awaiting CAB. A new CAB will be created, this is a copy of the original SD ticket including description and last comment.

One of the two following conditions must be met to create a CAB issue.

1. Bugfix to deliver a functional/technical solution for the original SD issue. SD issue remains open until the fix has been applied.
2. Non-bugfix for internal improvement, prevent (recurring) issues for the future. SD issue can be closed, user will be informed that current issue is fixed but there will still be worked on in the background to prevent from happening again or improvements.
   To set status back of SD ticket to In Progress use Button Workflow - CAB Pending, SD to be closed
   
   1. Use comment: Internal or Respond to Customer (default is Internal comment, respond to customer triggers notification to be send to the Reporter and Participants)
   2. Add comment (not mandatory can also be left blank)
   3. Click CAB Pending, SD to be closed button
      
      
      
3. Close SD 

Decline CAB

If Issue was solved and CAB is not needed anymore, the CAB can be declined.
This can be done by selecting the Declined button.


Select Fix version in the nearest future date, this will trigger automatically cleanup of the CAB Board after passing the fix date.

CAB issue is updated to status Declined

Development issue creation via CAB

Per (sub)department a development project is existing in Jira: B2B-Apps - Ympact / B2B-Apps - Ympulse / B2B-Apps - BA / B2B-Apps - Logistics / B2C-Apps

A Development issue is automatically created when a CAB issue is approved.
The Development issue will automatically be linked to the CAB and original SD issue.

• Development issue created, linked SD issue will be automatically updated to status AWAITING DEVELOPMENT
• Bugfix: Original SD issue remains open until Development issue is closed, the SD issue will be updated to status READY TO CLOSE.
• Non-bugfix: Internal improvement, prevent (recurring) issues for the future. SD issue is already closed. 

Installation instructions: Need to be added to the Development ticket before it is set to status READY FOR MERGE.

Function design (FD) and Technical design (TD) documents can be found in Confluence under space  Functional Conceptional Designs.
At the main page instructions can be found how a Functional/Technical Conceptional Design document can be created (via standardized template).