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 #36485 have custom services to /projects/:id/project_services
    Actions
    Summary
    Empty
    have custom services to /projects/:id/project_services
    Empty

    To avoid breaking change and make the upkeep less painful in the future, the existing representation will be used.

    The new key is_custom will help the user to distinguish custom service with 'classical' service.

    In addition to Tuleap defined services, the custom services will be added with the following format.

    {
    "id": 2613,
    "label": "My custom service",
    "name": "",
    "is_enabled": true,
    "icon": ""
    "url": "https://...",
    "uri": "project_services/2613",
    "is_custom": true
  }
    Empty
    Empty
    Status
    API
    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
    #36485
    Manuel Vacelet (vaceletm)
    2024-02-09 09:47
    2024-02-01 16:34
    30822

    References
    Referencing story #36485

    Artifact Tracker v5

    rel #35498 15.6

    Git commit

    tuleap/tuleap/stable

    Add `is_custom` and `url` keys in the REST service representation e2d4daa37e
    User avatar Clarck Robinson (robinsoc) , 2024-02-07 12:39
    refacto: stop using the same representation for PUT and GET REST route 37b3fb26e6
    User avatar Clarck Robinson (robinsoc) , 2024-02-08 15:21
    Referenced by story #36485

    Other

    gerrit #30380
    gerrit #30394
    Display settings

    Follow-ups

    User avatar
    Clarck Robinson (robinsoc)2024-02-06 11:00
    • 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