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 #11407 have a test environment with my username and password
Actions
Summary
Empty
have a test environment with my username and password
Empty
  • Username and password is given as an input of the REST route
  • There are REST tests
  • 3rd party can submit its own project archive for creation
Empty
Empty
Status
Empty
Done
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
#11407
Manuel Vacelet (vaceletm)
2018-04-19 11:26
2018-04-16 14:37
11520

References
Artifact links
Empty
Referencing story #11407

Artifact Tracker v5

epic #10175 User Onboarding
rel #10995 10.0

Git commit

tuleap/tuleap/stable

User password is provided to REST route 302eb6f7ee
User avatar Manuel Vacelet (vaceletm) , 2018-04-16 14:43
User login is provided to the REST route 5eca7c637c
User avatar Manuel Vacelet (vaceletm) , 2018-04-17 14:27
Package plugin create_test_env bada6f2a2a
User avatar Manuel Vacelet (vaceletm) , 2018-04-17 14:29
Allow consumer of create_test_env to choose which archive is used 78c83e9512
User avatar Manuel Vacelet (vaceletm) , 2018-04-19 09:01
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2018-04-16 16:59
  • 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
  • Status changed from Ready (stalled) to On going