Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-20355

Resources should be shared between plans.


    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.

      Atlassian Update - 24 March 2016

      Hi everyone,

      Thanks for voting and commenting! This issue is being addressed as part of the all new Portfolio live plans, which feature an entirely overhauled and more seamless integration model with JIRA Software / Agile. Live plans are currently available as a labs feature for both Server* and Cloud, so you can start evaluating them without any risk of impacting existing Portfolio plans. They are not yet feature-complete, we're working on bringing all major capabilities of standard plans back into live plans on top of the new integration model before we graduate live plans out of labs and make them the new standard way of working.
      Please check out this blog for a summary and short videos of how the top-voted suggestions are being addressed with live plans: Top 10 suggestions addressed in live plans and join our Portfolio Pioneers LinkedIn group to discuss feedback and best practices!

      Martin Suntinger
      Principal Product Manager, Portfolio for JIRA

      *The live plans labs feature is available with Portfolio for JIRA 1.12 or higher. It is compatible with JIRA Software 7.0.5 or higher, and JIRA 6.3 or higher, in association with JIRA Agile 6.7.12 or higher.

      Currently, resources cannot be shared between plans. As the doc explains:

      "plans are completely logically separate and do not consider in any way data from other plans. This means, that the same user could be booked in parallel plans for the same time slot."

      Here are some unfortunate consequences:

      • JPO could not be used by an organization of any size for global resource planning.
      • If one is trying to use JPO for an area with a number of independent projects and shared resources, there is no good solution:
        • If you throw everything into one big plan, you make "plan updates" problematic, since the results affect the entire plan and may need to be coordinated with many different people who are supposed to be working independently of each other - probably impractical. Furthermore, by mixing independent projects into one plan, you make the plan too "big" for comfort. (But it is true that JPO offers features like release streams and initiatives that help here. However, it looks like JPO might provide sub-plan objects like release streams to work around the problem that plans have to be bigger than they naturally would be, due to the fact that resource sharing is not possible. ).
        • If you create separate plans, you have problems allocating resources. You have to be careful to look at how a person is allocated in each plan to make sure the allocation doesn't exceed his total available hours. And you have make arrangements for him not being overbooked for a given period of time. All this without JPO support.

      I think the solution is to move the "People" feature out of the plan and into a bigger object - e.g. "Organization". Here one would specify people and allocate them for given periods of time to plans. The plans would then have to work with the resource constraints handed down from the organization.

            Unassigned Unassigned
            aafa195bfd98 Intel CHD Jira Admin
            27 Vote for this issue
            14 Start watching this issue