•  
     
    story #5645 Cherry pick certain artifacts to add to the Backlog
Summary
Empty
Cherry pick certain artifacts to add to the Backlog
they can be planned into a release and then in a sprint.

Background: As an example, users of our application would submit a Feature Request using the tracker interface. As product responsible, if the new feature makes sense, we want to add it to our Backlog. If it is not valid, we will just update the tracker and go back to the user. We do not want to pollute the backlog with unwanted artifacts.

This story depends on both story #6283 and story #6307

Backlog listing

  • The backlog section is displayed only if there is something to interact with (at least one backlog or milestone)
  • When the artifact doesn't already belong to a backlog, a selectbox is show (see mock-up)
  • In the first part of the selectbox, the top backlogs are displayed (there is at least one: to be planned) other can be created as per story #6277
  • I cannot move from one milestone to another in one click. I first need to remove myself from a milestone and then I can be moved in another one
  • I see only the "Current" and "Next" milestones
  • I see only the milestones I can be moved in (according to my parent and planning configuration)

Use cases

Given following setup:

Release_2
Release_1
|-- Sprint_2
`-- Sprint_1

Epic_1
Epic_2 (in Release_1 backlog)
|-- Story_2 (in Sprint_1 backlog)
`-- Story_1
Story_3
Request_1
Epic_3
`-- Story_4

In addition to that, the planning configuration tells that:

  • Release backlog is made of Epics or Requests
  • Sprint backlog is made of Stories or Requests

What will I see in my "Backlog" selectbox (see 4-agile-dashboard-cherry-pick-select.png mockup):

  • When I browse Epic_1: Top backlogs | Release_1 | Release_2
  • When I browse Epic_2: Already in a Release_1 backlog. Cannot be removed. Cannot be moved elsewhere (because subelements are already planned in submilestones)
  • When I browse Story_2: Already in Sprint_1 backlog. Can be removed or moved in Sprint_1 backlog
  • When I browse Story_1: Sprint_1 | Sprint_2
  • When I browse Story_3: Sprint_1 | Sprint_2
  • When I browse Request_1: Release_1 | Release_2 (Note: cannot be planned in a sprint without being planned in Release first)
  • When I browse Epic_3: Top backlogs | Release_1 | Release_2
  • When I browse Story_4: No backlog available (Note: cannot be planned because its parent is not yet planned)
Emilio Palmiero (empa)
Status
Empty
Canceled
Development
  • [x] Does it involves User Interface? 
  • [x] Are there any mockups?
  • [x] Are permissions checked?
  • [x] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#5645
Patricia Carrasco (pcar)
2018-07-17 11:10
2013-11-26 16:20
4830

References

Follow-ups

User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Permissions cleared
User avatar
For the record, the tricky part is to properly list the milestone candidates (in which milestone I can be placed/moved)

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Checklist set to Does it involves User Interface? , Are there any mockups?, Are permissions checked?, Does it need Javascript development?
User avatar

Manuel, could you please provide clarification on the following statement as per above: "I cannot move from one milestone to another in one click. I first need to remove myself from a milestone and then I can be moved in another one". How will this be accomplished?

When a backlog element (let say story_1) is already a backlog of a milestone (let say a sprint_1) and you want to move this story to another sprint (Sprint_2), you would have to (on Story_1 artifact):

  1. Untick "Sprint_1" from the "Backlog" selectbox
  2. Update the artifact
  3. Tick "Sprint_2" in "Backlog" selectbox
  4. Update the artifact

Do you think it's an acceptable behaviour or do we need to take into account the possibility to switch from one milestone to another in 1 step. For instance with a sequence like:

  1. Untick "Sprint_1" from the "Backlog" selectbox
  2. Tick "Sprint_2" in "Backlog" selectbox
  3. Update the artifact

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Checklist cleared values: Does it involves User Interface? , Are there any mockups?, Are permissions checked?, Does it need Javascript development?
User avatar
Artifact view modification was extracted in story #6307

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Checklist set to Does it involves User Interface? , Are there any mockups?, Are permissions checked?, Does it need Javascript development?
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Manuel, could you please provide clarification on the following statement as per above: "I cannot move from one milestone to another in one click. I first need to remove myself from a milestone and then I can be moved in another one". How will this be accomplished?

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Patrica,

I updated the use cases for the cherry-pick in artifact, could you please review them and tell me if it corresponds to what you expect ?

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Currently what is displayed in the Backlog(s) is defined in the Agile Dashboard Admin. Once the tracker type is associated then all artifacts of that tracker are displayed in backlog. We should also make it possible from the tracker to associate certain artifacts to the backlog (for example, selected Requests, Feature Requests or bugs etc.). This story probably will have an impact or dependency on story #5065.
User avatar

Given a Planning organization like:

Top Backlog
|-- Product A
|   |-- Release 1
|   |   |-- Sprint 1.1
|   |   `-- Sprint 1.2
|   `-- Release 2
`-- Product B

Does it means that user wants:

  • a "Top backlog" with only  selected artifacts
  • or that he wants, from within the tracker (when he is browsing an artifact) to add the current artifact in one of (Top Backlog | Product * Backlog | Release * Backlog | Sprint * Backlog) ?