Mindbending #1 | I am a workspace owner but I am unable to add features to my roadmap.

[VijayG]

Unable to add Features/Roadmap items to a Product space despite being the owner

Hi Atlassian Community,

I’m facing what appears to be an account/workspace access issue within Atlassian Product Discovery and would appreciate some guidance.

I am the owner of the Product space within my org for our product, X. However, I’m currently unable to add additional Features, Ideas, or Roadmap items within that Product space.

I’ve tried troubleshooting this multiple times, but I suspect the issue may be connected to how my Atlassian account and workspaces were originally configured.

Before selecting Atlassian for Product Management, I was experimenting with several tools and setups. During that process, I ended up creating two separate Atlassian workspaces/sites. My concern is that my account permissions, Product Discovery access, or organization ownership may now be associated differently across these two environments.

Could someone help me understand:

• Can having two Atlassian workspaces/sites associated with the same account create this kind of permissions issue?

• How can I confirm which organization/workspace actually owns the BrahmEdge-PD Product Discovery space?

• How can I verify whether my account has the correct Product Discovery permissions, even though I am shown as the Product space owner?

• Is it possible to consolidate or remove the duplicate/unused workspace without affecting our active Product Discovery setup?

• Has anyone encountered a similar issue where they appeared to have ownership/access but were still unable to create new Product Discovery items?

There are also two additional observations that make me suspect that the problem may be related to the organization/workspace configuration:

Suspicion 1: Atlassian is currently unable to verify my company URL/domain. This makes me wonder whether my company, organization, or workspace association has not been configured correctly.

Suspicion 2: Our Atlassian Admin has already invited me to the relevant workspace, and I have access to it, but I am still unable to add new items within the Product space. This makes me think the issue may be deeper than simply being invited to the workspace and could involve Product Discovery permissions, site access, or organization-level configuration.

Due to company security and privacy requirements, I’m unable to attach screenshots or expose our internal Atlassian configuration on a public Community post. However, if an Atlassian Support representative needs specific account, workspace, or configuration details to diagnose the issue, I would be happy to provide the relevant information through an appropriate private/support channel.

Could someone please help me determine whether my hypothesis about the two workspaces is correct, or point me toward the specific permissions/configuration I should check?

Thanks in advance for your help.

[Tanguy Crusson · Accepted solution]

Hi @VijayG , I think what's possible is that your admin gave you access to the JPD app on the site (as in: a license) but you don't have access to the space as a creator or space admin. you should ask your admin to open the space, go in space settings, and add you there with the space role "space admin" or "creator"

You shouldn't face any issues of having multiple sites. I have more than 50 :) 

[VijayG]

Thank you for the assist. I was able to secure the JPD access a while ago. 

[Jean Horn · Accepted solution]

👋 Hi VijayG!

I completely understand how frustrating permission issues can be, especially when you are listed as the space owner. Let’s break down your questions to help you get this sorted out:

1. Can having two workspaces/sites under the same account cause this permission issue?

A: When you have more than one site or organization associated with the same account, the permission settings are completely individual to each site. Having two sites won't directly cause a technical glitch, but it’s very common to accidentally be logged into or working under a site where your product role is different from what you expect.

2. How can I confirm which organization/site owns the BrahmEdge-PD space?

A: The easiest way to confirm which environment you are currently in is by checking your browser’s URL bar.

Look at the domain prefix: https://your-site-name.atlassian.net. This clearly identifies which Atlassian site is hosting the BrahmEdge-PD space.

3. How can I check if my account has the correct Product Discovery permissions?

A: In Jira Product Discovery (JPD), being the owner of the space does not automatically grant item creation rights if your assigned product role isn't configured for it.

To check this:

1. Go to your product space and navigate to Space Settings > Access.
2. Check your assigned role (Administrator, Creator, or Contributor).
3. Both Administrator and Creator roles can create ideas by default. However, if your role is set to Contributor, you won't be able to create ideas unless enabled under Space Settings > Features > Create ideas.
4. Additional tip: Ask your Atlassian Admin to check admin.atlassian.net and ensure your user account has an active Creator product license assigned for Jira Product Discovery on that specific site.

4. Can the duplicate/unused workspace be removed?

A: To give you the best advice on this, could you clarify what you mean by workspace?

• Are you referring to a Space/Project within the same site, or an entire Atlassian site/organization (e.g., another .atlassian.net URL)?

(If it's an entire unused site, an organization admin can safely delete or deactivate it without affecting your active site, provided no critical data lives there).

Regarding your additional concerns (Domain & Support):

• Domain Verification: Domain verification in Atlassian Access is used for centralized user management (SSO/account claiming). Not having it verified will not block you from creating ideas or using JPD.
• Support: Since you cannot share screenshots publicly due to privacy policies, if checking Space Settings > Access doesn't solve it, your Atlassian Admin can open a private support ticket directly with Atlassian at support.atlassian.com to investigate safely.

Hope this helps narrow down the issue! Let us know your clarification on point 4 so we can guide you further. 😁