Do you want to be able to change Comment security defaults? Now you can
Specify security defaults globally
Specify security defaults for a project
Force Selection of role if default is not present
Specify the defaults security role for comments for all projects. Service Desk features only available for Service Desk 3
Specify the defaults security role for comments for particular projects. This will override any globally defined security defaults for this project.
If the default role you specify is not present then you can force the user to make a selection.
More details
This plugin allows you to set the default security level for comments and/or change the color of the comment field to highlight visibility. The settings can be applied globally for all Jira projects and/or at the project level.
Specify different defaults for:
- Add comment
- Add attachment
- Log work
- Link issues
- Edit Issue
- Assign Issue
- Transitions (also specify per-transition defaults)
If the role specified as the default is not in the role list then you are able to force the user to select a value.
.
Set the background and/or border color of the comment field for comments that are "Viewable to all users" or all the other security settings.
.
Restrict access to which users will get default values.
.
Service Desk customers can now have basic security defaults (add/edit comment, transitions and log work) for internal comments. Colorization of comments are also available for these screens.
.
NOTE:
- Any feature requests are welcome
- This WILL work on the Jira Agile (Greenhopper) plugin screens
Reviews for cloud
(7)Sign in to write a review
Hi Gerda. I'll add it to my list of things to do (assuming it possible).
EDIT: Hi Gerda, was hoping to add for JIRA 7 but there is still no way to know if a comment was from an email. Because of this I can't implement this. Will keep checking in the future.
Reviews for server
(7)Sign in to write a review
Hi Gerda. I'll add it to my list of things to do (assuming it possible).
EDIT: Hi Gerda, was hoping to add for JIRA 7 but there is still no way to know if a comment was from an email. Because of this I can't implement this. Will keep checking in the future.
Pricing
| 10 users$10 | 25 users$50 | 50 users$90 | 100 users$160 | 250 users$480 | 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.
Redmoon Software Ltd provides support for this app.
Vendor support resources
Find out how this app works.
Versions
Version 2.11.1 • Jira Server 7.0.0 - 7.10.1 • Released 2018-06-07
Summary
Fixed bug with security in Service Desk Attachments screen
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 Comment Security Default 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 Comment Security Default. You're prompted to log into MyAtlassian. Comment Security Default 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 Comment Security Default versions compatible with your instance, you can look through our version history page.
Similar apps
