Real-work scenario of contributors not being able to edit idea
Asked by David:

We are about to go live with a new product discovery project. I understand the difference between a creator role and a contributor role. I have two use cases that I could use some help with.

1. We have an automation rule that creates an idea from a JSM issue. However, the support agent does not have a creator role so they cannot edit the summary. Often times, the summary our customers send needs to be updated to something that makes sense.
2. This is a variation of #1 above. Most of our employees will be contributors so they can add ideas. However, once the idea is created, they can't make changes to the summary or description.

What I'm trying to avoid is a lot of work on the product team to have to fix mistakes or make simple updates to the summary or description. However, I don't want to give all our employees creator access. For 1, that's more money for licenses just to update simple things, and 2, I don't want them to be able to edit/add views.

Does anyone have a recommendation?

It seems to be there is a missing role or that the contributor role should be slightly updated. If a contributor can add an idea, it seems like they should (at a minimum) be able to edit ideas they created. I don't want them to have greater access to edit/create views. Without this, I will spend a lot of time asking them to tell me the change that needs to be made so I can make it for them. That doesn't help me save time. That adds a lot of wasted time to my day.

Thanks for any help you can provide!


Answers:
author: Katrina Prior
body: Hi there! You can create custom roles in JPD that allow permissions on a task by task basis. We had a similar use case and created a 'Contributor Plus' role that allows some contributors to edit issues. Within Settings \> Access you can select Manage Roles and 'Create new role' to add additional permissions.

Note - some of these editing permissions are marked 'CREATOR' which I thought may restrict non-licensed users from being able to actually complete the tasks and which causes a little exclamation point error to show up on the permissions list. However, so far we haven't had that issue.

comments: author: David
body: Awesome, I will give this a try tomorrow and hopefully it gives me what I think. Thanks!!


author: Angie Adams
body: [@Katrina Prior](/t5/user/viewprofilepage/user-id/5411675) Do you get charged the creator license fee for those users?


author: Gary Spross
body: I'm glad this works for you, but I see 2 issues:

* Contributors will be able to edit ANY idea, not just the ones they've created
* Atlassian could make a change that undermines this work around, especially since it is indicated that the edit permission would need "Creator" level access

Personally, I'd like to see Atlassian update this to allow Contributors to be able to edit their own ideas and then the project permissions could be set more restrictive if necessary to not allow editing by Contributors if desired.


author: Katrina Prior
body: We have not be charged a Creator license for those users, but as Gary mentioned there's nothing to say we won't in the future or the ability to grant these privileges to non-creators will be revoked. Gary is also correct that you cannot specify currently which ideas users are able to edit.


author: David
body: [@Katrina Prior](/t5/user/viewprofilepage/user-id/5411675) - Do you have a free or paid version of JPD? Currently, we have a free version which does not allow me to create custom roles. I haven't been able to figure out yet how to switch to a paid version in order to test this out. I have a question out to Atlassian Support on this.


author: Katrina Prior
body: Hi [@David](/t5/user/viewprofilepage/user-id/3682781) - Sorry for any confusion, we do have the paid version. For our account, we just needed a site admin to turn it on in the overall Jira admin settings.