Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #6283 have a dedicated backlog
Actions
Summary
Product Owner
have a dedicated backlog
Empty
  • New dedicated object to manage backlog
  • There is 1 backlog by default, the one on the right of the screen (the one that feed the planning). This backlog cannot be removed
  • Forgeupgrade to import existing backlog
  • Limit the number of backlogs 4
  • The backlogs are ordered (stories goes from the left to the right)
  • As admin, I can order backlog
  • There are write permissions on the backlog (ie. only the PO can drag stories into "to be estimated")
  • REST: /projects/:id/backlog should still return/manage the "Content" pane (ie. the backlog on the right)
  • We do not manage other backlog via REST
  • Take into account duplicate and XML import / Export

Things to take into account

  • Deletion of artifact should delete into backlog too (delete link)
Empty
Empty
Status
Empty
Canceled
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] 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
#6283
Manuel Vacelet (vaceletm)
2018-07-17 11:10
2014-02-24 10:34
4830

References
Artifact links
Empty
Referencing story #6283

Artifact Tracker v5

epic #6308 Backlog Cherry-picking
story #5645 Cherry pick certain artifacts to add to the Backlog
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2015-07-22 11:40
  • 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