easeContext - Context Manager for Jira
OVERALL RATINGS
INSTALLS
33
SUPPORT
- Partner Supported
Key highlights of the appAllow Project Admins to manage the context of custom fields without system admin rights
Create Project Specific Context
Allow project administrators to create the project specific context for custom fields. Add, modify, delete, and enable/disable the field context.
Limit Project Specific Context to Selected Project
Project specific custom field options can be restricted to the project for which they are configured. This ensures that other projects are not affected.
Migrate Project Specific Context to Global Context
Project specific custom field options can be migrated to global scope. After the migration, the new field context will be available for all Jira projects.
Supporting media
More details
CM4J - Context Manager for Jira enhances the project management aspect for single projects.
It allows the Jira project administrator to configure own project specific custom field context without alignment with the Jira system administrator. This gives freedom to the project administrator to configure custom field context that affects only the project itself.
Key Features:
- Custom field configuration on project level
- Limit custom field option to those your project needs.
- Migrate back project field contexts to global context for all projects
Resources
Download
Get the .jar file downloaded to your system
App documentation
Comprehensive set of documentation from the partner on how this app works
EULA
Get the End User License Agreement for this app
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policy
Security program
This app is not part of the Marketplace Bug Bounty program.
Version information
Version 2.6.3-4•for Jira Data Center 9.4.0 - 9.17.4
Release date
Jun 21st 2024
Summary
Improvements and bugfixes to configurations
Details
This release highlights the following features:
- Unblocked “HTTP Status 400 - Bad Request” page when accessing and configuring custom fields
- Excluded custom field types from “Checklist for Jira” third-party plugin
- Bugfixes for context in configurations
See our release notes for more details.
Payment model
Paid via Atlassian