JIRA Cloud - What site to use for testing now that free site permissions are disabled

Hi, anyone in the community have a suggestion for where to do testing if your addon needs to respect JIRA group/role permissions? Our existing test site just flipped to the new “Free” plan which disabled all permissions so now we cannot test that functionality.

Thanks in advance,

1 Like

Hi @Chris_at_DigitalRose,

This is a good question. I’ve also been impacted by this when trying to reproduce issues. Unfortunately I don’t have an answer right now, but I’ll bring this up with our team. Until then, it would be great to hear from the developer community if they have thoughts on this.



Hi @dmorrow,
I actually raised a similar issue with Sunny about adding Premium features (advanced roadmaps in particular) to the dev instances. I believe the dev instances should still have a limited number of users but should offer full Premium functionality (which of course also includes Standard functionality).

Are sites created by http://go.atlassian.com/cloud-dev affected? I couldn’t quite work out, but it looks like there is some kind of discount applied to the standard plan.

On premium, it would be really valuable to be able to test against premium, and by this I mean have multiple premium instances we can use for automated and exploratory testing for testing different environments.

@Chris_at_DigitalRose was the instance that flipped over to the free plan, one of Cloud Developer Bundle (5 user) instances? If so, please DM me your instance name.

@jmort the Cloud Developer Bundle (http://go.atlassian.com/cloud-dev) should contain all advanced permissions features of an instance on the Standard plan.

@david2 agree with your statement re: dev instances and Premium features. I’ve started working on that, and hope to provide an update/progress over the next several weeks.


Thanks @nmansilla!
To be clear, our biggest issue right now is that our app supports Advanced Roadmaps, and when it was still an app (Jira Portfolio), we were able to activate a trial any time we need to work on Portfolio-specific features. Now we can’t, and we have to start a new Jira Premium trial every time (and import data and configuration) which is very inconvenient.

Thanks for confirming, it is what we’re observing too.