Setup and Customization
Accessing and configuring the Appvibe Feature Rollout Planner in Jira enables you to customize how feature launches are managed within your projects. Navigate to Manage Apps, locate the app, and click on the Configuration button to begin the setup. This setup page allows you to manage Roles and Permissions, view System Fields, define Custom Fields, and configure Conditional Formatting.
Roles and Permissions
The Appvibe Feature Rollout Planner supports three distinct roles:
- Admin: Grants full access, including configuration and setup options. Admins can assign roles to Jira groups.
- Editor: Allows users to update and view Feature Rollout Planner data.
- Viewer: Permits users to view data without making updates.
Jira Administrators have automatic access to the Feature Rollout Planner configuration screens.
System Fields
The app comes with predefined fields essential for feature rollout planning. These fields include:
- Feature Name
- Launch Date
- Responsible Team
- Status
- Marketing Plan
- Dependencies
- Tags
These fields form the foundation of your feature rollout data.
Custom Fields
To tailor the planner to your specific needs, you can create additional fields by selecting the Add Field button. Configuration options include:
- Field Key: A unique identifier for the field.
- Field Label: User-friendly name for the field.
- Field Type: Choose from Text, Number, Date, Select, or Multi-Select.
- Required: Set whether this field is mandatory.
- Sortable: Enable sorting for this field.
- Filterable: Enable filtering for this field.
Conditional Formatting
Conditional Formatting lets you customize data presentation based on certain criteria. Set conditions based on field values; if met, adjust label styles and highlight colors accordingly.
Summary
Configuring the Appvibe Feature Rollout Planner equips your team with a versatile tool for tracking and managing feature releases. By defining roles, customizing fields, and employing conditional formatting, you can ensure a streamlined and transparent rollout process within your Jira environment.
No Comments