Hello everyone :-)
We are studying the possibility of installing JPD on our production instance in order to link jpd and our backlogs under JIRA.
However, with each new JPD project, it creates new fields, which are all available as many times as there are projects in the list of available fields for e.g. gadgets ... search ticket views...
How do you work with this constraint in projects combining JPD and jira?
Thank you for your feedback :-)
Olivier
Hello Olivier,
We received this feedback from our customers and we are currently addressing it. You can find it mentionned under the item Use a project as a template to create other projects
of our public roadmap.
We will ship this enhancement in the upcoming months: only one of each field will be created, regardless the number of projects you'll have. You won't need to migrate anything.
Stay tuned in community or our roadmap to be aware of the release of thefeature.
Cheers,
Best Regards,
Hermance
Product Manager @ Jira Product Discovery
The roadmap link you provided appears to be the internal one for Atlassian team members. Did you instead want to provide this one for the public view of the roadmap:
From this article:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes thank you, I changed the link in my comment.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
From my perspective, JPD is based upon team-managed projects (TMP), and thus you are correct: many of the project-specific, custom fields are unique for each project.
There are several ways to mitigate those differences:
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello to both of you, thank you for your comprehensive and detailed feedback.
It gives us confidence in our ability to offer this solution to new users without impacting existing ones.
And yes Bill, I think we'll definitely use global fields, but a single project will be too complicated because we have so many different entities.
I keep the idea of automation between projects in the back of my mind.
Best Regards,
Olivier
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.