Hi everybody!
This week I've found out Atlassian is starting an exploration around company-managed projects. You can find this information here.
If you miss company-managed projects in JPD, please participate in this initiative, so that Atlassian can explore the problems you're facing.
Thank you.
Hi @Hana Kučerová
That is interesting news, and I am curious how that might work regarding the current model of Creator permissions (and licensing costs). Likely there are many challenges / differences to address...
JPD seems built upon team-managed projects (TMP), essentially allowing someone with at least project admin permissions to do just about anything to the JPD fields, views, and features, but not the referenced global / company-managed (CMP) fields. Indeed some global fields are still not supported (or supported poorly) when referenced in a JPD project configuration. And don't get me started on the JQL and dashboard challenges of referencing TMP and JPD fields ;^)
If a JPD project admin had access to global / company-managed fields the same way they do in JPD, they could impact the fields / behaviors in a manner that overlaps Site Admins (or higher) for other projects. Or will there be a new subset to Site Admin also, but with additional licensing charges? And so on...
Interesting idea and I am curious to learn where it leads.
Kind regards,Bill
Thank you, @Bill Sheboy .
It looks like you're new here. Sign in or register to get started.
