Change Requests #

Change requests are the fundamental units of work in BlueRequests. They represent any changes that an organization wants to implement, from new features to bug fixes and infrastructure improvements.

Change Request Attributes #

Every change request contains the following key attributes:

Core Information #

Title: Descriptive name for the change
Description: Detailed explanation of what needs to be changed
Type: Classification (Feature, Bug Fix, Enhancement, etc.)
Priority: Urgency level (Low, Medium, High, Critical)

Workflow Management #

Status: Current state (Draft, In Progress, Review, Approved, Completed)
Stage: Current development stage in the workflow
Stage Owner: Team member responsible for the current stage
Stage Status: Progress indicator within the current stage

Project Context #

Project: Parent project this change belongs to
Platform: Target deployment platform or environment
Release: Planned or assigned release version

Change Request Details Screen #

The change request details screen provides comprehensive information and is organized into several key sections:

Detail Section #

Purpose: Display comprehensive details of the change request including description, impact, and requestor information.

Key Elements:

Request Description: Detailed explanation of the change
Impact Assessment: Information on how the change affects the project
Attachments/References: Supporting documents or images
Metadata: Creation date, last modified, requestor information

Stage Workflow Section #

Purpose: Outline the stages and workflow of the change request process.

Key Elements:

Stage Indicators: Visual cues indicating current and completed stages
Stage Descriptions: Brief details on what each stage entails
Action Buttons: Options to move the request to the next stage
Approval Gates: Required approvals at each stage

Usage Tips:

Follow the workflow to understand the progress and next steps
Review stage details for clarity on process expectations
Use action buttons to advance the request when appropriate

Comments Section #

Purpose: Enable collaboration and discussion regarding the change request.

Key Elements:

Comment Thread: Displays a chronological list of comments
Add Comment Box: Field to add new comments
Timestamp/Author: Information on when and who made a comment
Mention System: Tag team members for notifications

Usage Tips:

Engage in discussions by replying or adding new comments
Monitor timestamps to stay updated with recent activities
Use mentions (@username) to notify specific team members

Timeline Section #

Purpose: Provide a chronological history of events related to the change request.

Key Elements:

Timeline Events: List of all significant events (creation, updates, approvals)
Event Descriptions: Brief descriptions of each event
User Actions: Track who performed each action
System Events: Automated notifications and status changes

Usage Tips:

Use the timeline to track the progress of the change request
Refer back to earlier events for context on decisions made
Export timeline data for reporting and analysis

Best Practices #

Creating Effective Change Requests #

Clear Titles: Use descriptive titles that explain the purpose
Detailed Descriptions: Provide sufficient context and requirements
Proper Classification: Choose appropriate type and priority
Impact Analysis: Document potential effects on existing systems

Managing Change Requests #

Regular Updates: Keep status and progress current
Active Collaboration: Engage with team members through comments
Documentation: Maintain clear records of decisions and changes
Quality Gates: Ensure proper review at each stage

Navigate to other sections to learn about Projects, Releases, and Messages that work together with Change Requests.