Our Board enables you to drag and drop issues across the board and by doing so will affect the status of the issue or create a release of the issues or publish the issue linked file into a publication environment as set up by your administrators.

Please Note: Moving an issue across the board means that notifications will be sent to the reporter and interested parties identified on the issue.

Generally, publication environments support the development process as follows:

DEV

The DEV environment is the Development environment where all files should be checked-out to when you wish to develop them further. The development environment generally would be a development node or stream in Qlik Sense or a shared development folder in QlikView.

The development environment generally would not allow for business users to access it, but would purely be for developers to investigate, apply fixes and perform their own testing before they release a file to the business user for testing.

In the Board this method of work is supported enabling the developer to move his issue and associated file across the board based on his development process. Issues can move either left or right across the board and dropping them into certain statuses on the board will change the status of the issue accordingly.

To Do Column

The To Do column provides two options when you drag your issue across the Board . Dropping your issue into these highlighted areas called bands will change the status of the issue accordingly.

• Open Band

  • Whenever a new issue is created it will be posted into the DEV stream with a status of Open.

• Reopen Band

  • The reopen band change is used for issues that have been rejected or resolved before so that issues can be reopened subsequent to the decision being taken, and reopening the issue instead of creating a new issue means you can retain all historical changes and collaborations around the issue.

Done Column

The Done column provides three band options when you drag your issue across the Board . Dropping your issue into these highlighted bands will change the status of the issue accordingly.

• Rejected Band

  • The rejected band should be utilized for issues that have been rejected by either the developer, stakeholder and or business user.

• Resolved Band

  • Resolved means that the issue has been resolved through a fix or it could not be replicated but the requestor has accepted that the issue can be resolved. Resolving the issue keeps the issue in the stream so you should deactivate the issue if you wish it to be removed from the board.

• Create Release Band

  • Please Note: Business Users are not able to create a release

  • When you drop your issue into the Create Release band the WIP system will create a release of the issue and place it into the UAT stream with an Open status.

  • Creating a release is the only way to move your issue to the UAT stream, and that is as a release of the work that is now ready for testing by the user.

UAT

The User Acceptance Testing (UAT) stream functions under the same columns of the Board and provides for three drop options within the Done column.

The user acceptance testing process is an iterative process between the developer and the user for testing the work that has been performed on the file. The developer will publish the file so that the testing user can access the file in the UAT/Test/Pre-PRD publication environment and will move the release across the UAT stream as the testing commences.

• Rejected Band

  • The rejected band should be utilized for issues that have been rejected by either the developer, stakeholder and or business user.

• Resolved Band

  • Resolved means that the issue has been resolved through a fix or it could not be replicated but the requestor has accepted that the issue can be resolved. Resolving the issue keeps the issue in the stream so you should deactivate the issue if you wish it to be removed from the board.

• Publish

  • Please Note: Business Users are not able to publish applications

  • The publish band enables the developer to publish the release into the production (PRD) environment.

  • Dropping the release into Publish will bring up the publication view which enables the user to publish the file to an environment.

A release can be dragged across to the PRD environment

PRD

The Production (PRD) stream functions under the same columns of the Board and provides for three drop options within the Done column.

• Rejected Band

  • The rejected band should be utilized for issues that have been rejected by either the developer, stakeholder and or business user.

• Resolved Band

  • Resolved means that the issue has been resolved through a fix or it could not be replicated but the requestor has accepted that the issue can be resolved. Resolving the issue keeps the issue in the stream so you should deactivate the issue if you wish it to be removed from the board.

• Publish

  • Please Note: Business Users are not able to publish applications

  • The publish band enables the developer to publish the release into the production (PRD) environment.

Dropping the release into Publish will bring up the publication view which enables the user to publish the file to an environment.