Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
sf3 sf3
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • OpsPortal
  • sf3sf3
  • Issues
  • #62

Closed
Open
Created Aug 22, 2019 by Cyril L'Orphelin@cyloOwner10 of 10 tasks completed10/10 tasks

[SOMBO] v1.1

Service order management back office improvements :

  • When a comment is added into Jira , an email should be sent to user (ask template to marketplace team)

  • Add a view of all service orders (no authorization based on service) with additionnal filters

  • Make some fields only readable in the summary of Jira issues ( ask list to shifters)

  • Adapt the list to the new structure of Jira issues ( master / slave - epic)

  • Adapt the workflow and the details on the type of ticket (epic or service order)

  • Remove the limitation to 100% in the service order values

  • Add the possiblity to edit / remove providers and to add free provider

  • Manage EUDAT use case : DPMT integration

  • Generate pages for service providers using tokens and send email with the url to inform them

  • Generate uid for service providers (cf uid in dpmt) and service order to create hidden pages

Edited Dec 18, 2019 by Cyril L'Orphelin
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
v5.1
Milestone
v5.1 (Past due)
Assign milestone
Time tracking