Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Creator cannot modify project road maps

Doug Shapiro
Contributor
July 8, 2025

Hi All,

We currently have the free version of JPD and are under the 3 Creator limit. I have verified that the project role one of our users has is that of Creator. Even though he is a creator and has access to our JPD project, he is unable to modify any of the project roadmaps. Like me (also a Creator), he should be able to drag and drop ideas from one column to another in the roadmap but he is read only.  If I try to share the roadmap with him, it shows he already has access as a Creator. Previous to this user, we had another Creator who had full access and created this roadmap but they have left the company.

Does anyone think they know what's going on? Since this user is shown as a Creator and has full access to this project (and the roadmap) why can't they modify the roadmap?

1 answer

1 accepted

0 votes
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 9, 2025

Hi @Doug Shapiro , are you sure this person has a license? if they don't you'll see it in the project settings > access screen (there will be a warning). 

If you give someone creator access to a project but they don't have a license, they can only perform contributor actions. From what you're describing I would guess that's what's happening. 

Doug Shapiro
Contributor
July 10, 2025

Thanks for the reply, Tanguy. Here's what I learned from support:

The user in question, had the project role set to "Contributor". Even though they have a Creator license (shown in the "Product Access" column), they only have Contributor permissions for this specific project. This was of course an oversight but the problem is that now everything is greyed out and I cannot change the permissions!

More on what support wrote and how to fix:

------------------
So, what happened here is that this project was created as a private project (meaning that users need to be individually added to it), but since then there was a change in the feature where project access levels can only be used for Standard and above plans (this was done by the product team to bring it more in-line with other Jira products that have the same restriction on their respective free plans).

Since your project was already set to private when the change happened, the system keeps the configuration from before but you can't change the individual roles.

So, how do we fix this?

There are a couple of ways:

1) Enable the Standard trial, change Michael's product role (Contributor -> Creator), and then cancel the trial to go back to the free plan.

2) Enable the Standard trial, change the project access level to open (so that all creators on the site have access to it) and then go back to the free plan.
-----------------------------

So, my bad for not realizing that when I added this user with a Creator license months ago, I did not realize that the role defaulted to Contributor and now with this unexpected change in product alignment, everything is locked and I can't change it. I will have to do the "Trial" thing to unlock and modify.

Hope this helps anyone else struggling with the recent change.
Best,
Doug

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events