Concourse Feedback


Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.


For immediate technical support, please follow this guidance to open a Service Now ticket.


Jira Cloud: PDM Work items L4-L6 Optimization in Jira

Hi Team,

during our preparation of guiding materials Salesforce Jira Cloud, we were working on work items hierarchy visualization and identified potential room for simplification in amount of work items.

As for now we have L1-L3 quite simple:

  • Stage

  • Sub-stage

  • Activity

However, post activation in the scope we have 3 different types of L4s (delivery artifacts and events), L5 (tasks) and L6 (sub-task) (9 work item types). Moreover, we have a often a confusion for users as in addition to PDM tasks and sub-tasks we have Jira Standard Tasks and Sub-tasks.

So in total we have 11 work items types that requires quite advanced management.

We have proposal how it can be simplified [few scenarios, depending on technical possibilities and limitations]. All information has graphical representation in the attached document

Element #1: 1 type of L4s instead of 3

We can have 1 elements as delivery artifact with additional field category (client, internal, event). If internal and event it can be by default automated to have security level as PwC Only.

Element #2: reduce amount of L5-L6.

If we have one type of L4, there is no need to have different types of L5-L6 per L4. In such case we can have two options:

2a. Use Jira Standard Tasks and Sub-Tasks instead of PDM specific. [limitation: sub-tasks cannot be created as independent work item].

2b. [if 2a not possible] Have one type of tasks and sub-tasks [instead of 3].

Effects:

1-2a: instead of 11 work items types we will have only 3.

1-2b: instead of 11 work item types we will have 5.

Both options requires some updates in processes and ways of working, however, from overall Jira management it should be much easier.

Benefits:

  1. Simplier, smaller items list​

  2. Wider use of standard Jira items and features​

  3. Limited use of custom items​

  4. Better visibility of PDM items in Jira structure​

Also, to avoid confusion between PDM work items and Jira Standard work items we recommend to add L1-L6 prefixes to PDM specific work items


Kind regards

Olek

  • Oleksandr Prokopiv
  • Feb 4 2026
  • In Review
Workspace Territory N/A
Technology Salesforce
  • Admin
    Kelly Hughes commented
    19 Feb 23:09

    Thank you for the thoughtful submission, Olek. This has been assigned to the Jira team for evaluation and they will reach out to determine next steps. If any additional feedback on this came from your Salesforce PDM sessions, please let us know!