•  
     
    story #10736 administrate artifact links type at project level
Summary
Empty
administrate artifact links type at project level
Empty
  • Artifact links v2 are allowed to all projects by default (no longer progressive deployment in site admin)
  • Project administrators can decide to turn AL v2 off and only have "not typed" links
    • The behaviour is then the same than when AL v2 was not activated for one project
    • This is a new "Administration" panel at tracker admin level with one pane dedicated to ALv2 management
    • In the pane there is a switch that allows to activate / desactivate ALv2 usage
  • Project administrators can choose to disable some some types at project level
    • System type "_is_child" cannot be disabled if project is using hierarchy
      • If "_is_child" is disabled, project cannot activate hierarchy
    • System type "covered_by" cannot be disable if project is using Test Management
      • If "covered_by" is disabled, project cannot activate TTM
    • Same for artifactfolder & "in_folder" type
  • For cross-project usage
    • Nothing is done, if one project that use a type points toward an artifact in a project that doesn't, the link will be displayed with the type
  • The configuration of allowed type is inherited at project duplication
  • Allowed/restricted types are set in XML import/export
    • <nature> is extended to have a "is_used" attribute
    • If natures are specified at import with "is_used" attribute, they are setting the configuration (XML override seetings from project inheritance)
  • At desactivation of a given nature, if there are artifacts that are using this type
    • No modification of the exisiting data is done (link remains with types)
    • At update of those artifacts, depending on what is the easier to implement
      • Either keep nature until artifact link field is updated
      • Or discard nature at first artifact update
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
#10736
Manuel Vacelet (vaceletm)
2017-11-08 11:20
2017-10-10 11:17
4557

References

Follow-ups

User avatar
  • 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
  • Permissions set to