Skip to content

Frank Schophuizen

My feedback

7 results found

  1. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Frank Schophuizen shared this idea  · 
  2. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. 7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    Frank Schophuizen commented  · 

    Thank you for your reaction.

    On alternative b), one custom field per structure is not a acceptable option. We are implementing SAFe (Scaled Agile Framework) with Jira, so we use issue links to link portfolio backlog items to program backlog items and program backlog items to team backlog items. For this we have multiple structure boards: 1 for portfolio, 1 for each release train, and 1 for each development team. Currently this is about 8 structure boards per business unit. We have multiple business units, so we will have many structure boards.

    Currently, we are not reporting the aggregated values because we cannot get them out of Jira. But we want to make reports about estimates on portfolio items based on the estimates of the issues on program and team level. Similarly for logged work. And we want progress on portfolio level based on the progress at program and team level.
    We want to have the logged work aggregated on portfolio level to be able to capitalize (in money) the costs of each portfolio item.

    Structure 3.0 supports multiple parents (or locations). We have not thought about that yet. But still a structure board will have Progress, Sum Estimate, Sum Remaining and Sum Logged Work columns, I presume, so I suppose you have given it some thought hoe to calculate those values.

    Regarding JQL: a function like structure() would be great.

    Frank Schophuizen shared this idea  · 
  7. 65 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Frank Schophuizen supported this idea  · 

Feedback and Knowledge Base