Allow Project Admins to manage the context of custom fields without system admin rights
Allow Project Admins to manage the context of custom fields without system admin rights
Create Project Specific Context
Limit Project Specific Context only to the project
Migrate Project Specific Context to Global Context
Allow project administrator to create the project specific context for Custom fields. Add, modify, delete, and enable/disable Project Specific Custom Field Context.
New Project Specific Custom Field Options can be restricted only to the project for which they are configured and ensure that other projects are not affected.
Project Specific Custom Field Options can be migrated to global scope. Post migration new Project Specific Custom Field Context will be available for all Jira projects.
More details
CM4J - Context Manager for Jira is built on Atlassian’s flagship product Jira, a powerful issue and project tracking tool. Atlassian tools are integrated better than ever to provide you with proven best practices, to seamlessly get from issue to code to deployment. By adding CM4J to your Atlassian environment, you will enhance the project management aspects. It allows Jira project administrator to configuration project specific custom field context and takes the burden out of the Jira administrator to configure clearly project-relevant custom fields. This gives freedom to the project's administrator to configure custom field context that affects only the project itselfKey Features:- Project Level Custom Field Configuration- Restrict the new Project Level Custom Field Context only to the project- Migrate the new Project Level Custom Field Context to Global Context
Reviews for cloud
(2)Sign in to write a review
Reviews for server
(2)Sign in to write a reviewPricing
| 10 users$10 | 25 users$120 | 50 users$220 | 100 users$400 | 250 users$800 | 500 & upAdditional pricing details |
Paid-via-Atlassian pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Do you offer academic, community, or open-source licenses?
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.
For more details about qualifying for special licenses, see here.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
ease solutions Pte Ltd is an Atlassian Verified vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 2.2.0-1 • Jira Server 6.3 - 7.9.2 • Released 2018-05-16
Summary
Limit scope to issue type
Details
It is now possible to limit the scope of a context to a given issue type(s).
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate CM4J - Context Manager for Jira via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for CM4J - Context Manager for Jira. You're prompted to log into MyAtlassian. CM4J - Context Manager for Jira begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older CM4J - Context Manager for Jira versions compatible with your instance, you can look through our version history page.
Similar apps
