epic #4952 REST API

story #4953 Spike: agree upon resources needed by Obéo

Artifact

Summary

As aEmpty

I want to *

Spike: agree upon resources needed by Obéo

So thatEmpty

Acceptance criteriaEmpty

AttachmentsEmpty

CC listEmpty

Status

CategoryEmpty

Status *Done

Development

Checklist

[ ] 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?

Technical informationsEmpty

Details

Artifact ID#4953

Submitted Bydylan bowden (dylan)

Last Modified On2013-09-16 11:16

Submitted On2013-09-11 08:50

Rank626

Permissions

Restrict access to this artifact for the following user groups:

References

Is related to

Artifact links

Reverse artifact links

Releases

Epics

Parent

Artifact ID	Project	Tracker	Summary	Status	Last Update Date	Submitted By	Assigned to
epic #4952	Tuleap	Epics	REST API	Closed	2015-22-07 11:23	dylan bowden (dylan)

Cross References

Referencing story #4953

Artifact Tracker v5

epic #4952 REST API

rel #4409 6.5

Show items referenced by story #4953

Referenced by story #4953

Artifact

art #4955

Follow-ups

Martin GOYOT (goyotm)

2013-09-16 11:16

Status changed from On going to Done
Category set to

Tracker Workflow Manager (forge__tracker_workflow_manager)

2013-09-11 09:30

Automatic change triggered by an update of art #4955.

Current artifact children satisfy the following condition(s):

at least one Tasks Status equals On going

Status changed from Ready (stalled) to On going

dylan bowden (dylan)

2013-09-11 09:13

Is related to
- Added:

dylan bowden (dylan)

2013-09-11 09:11

Is related to
- Added:

dylan bowden (dylan)

2013-09-11 09:11

Is related to
- Added:

Public

Artifact links

Reverse artifact links

Releases

Epics

Parent

Referencing story #4953

Artifact Tracker v5

Referenced by story #4953

Artifact

Follow-ups