With the inclusion of the global fields feature for JPD, we can utilize supported Jira custom fields within JPD projects now. YAY! However, I'm curious if it is on the roadmap to allow for adding contexts for JPD projects. I checked and JPD projects don't appear in the applicable projects select list when setting up a context. This would be an awesome addition so that, for select lists for example, the available options could be limited based on the project the field is applied to.
Hi Gary,
Contexts is a project attribute and applied through schemes. Projects that support contexts are only company-managed projects. Jira Product Discovery projects are only team-managed so it's not possible to add contexts to them, just like it is not possible for Jira Software team-managed projects either.
For the moment, it is not Atlassian roadmap to add contexts (or schemes) to team-manged projects, so it is unlikely that we implement this feature just for Jira Product Discovery projects.
@Hermance NDounga, thanks for the response.
Is it on Atlassian's roadmap to give the ability for JPD projects to be created as Company-managed? Outside of things like this example of contexts and schemes, there is also the more prevalent reason of having standardization in general. We are planning on standing up several JPD projects for our various teams and need a way to ensure some level of standardization across these types of projects. We don't utilize Team-managed style projects in JSW (or JSM) because of this inability to have standardization. We can certainly try to maintain standards, but having a Team-managed setup makes it very difficult to ensure adherence.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.