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 #12974 have several Contributors fields
Actions
Summary
tracker admin
have several Contributors fields

I can more clearly separate the responsabilities depending of the progress of my artifact.

Example of usage for level of support

  • I have 3 select assigned to fields in my artifact definition
    • "Assigned to triage"
    • "Assigned to analysis"
    • "Assigned to change"

At each step I have a list of people that might be assigned so

  • Triage people can follow the artifact progress from creation to end
  • "Change" people are only affected (and bothered) for the stage they are involved

Overview

This is an extension of "Contributor" semantic. The goal is to be able to statically defined more than 1 field.

The field that might be selected are still the same:

  • Select or multi-select of "users".

Functional overview

Contributor semantic is used in several places. The consequence of each are:

  • "Artifacts Assigned/Submitted" widget on personal dashboard
    • Updated to take the new fields into account
  • Tracker XML import/export
    • Updated.
  • Tracker duplication at project creation
    • Updated.
  • Tracker notifications
    • Updated. Take into account [Assigned to me] as well as global notifications rules (NB: need to ensure behaviour is consistent with the "notify" checkbox in the field config)
  • Cross tracker search
    • Updated. "@assigned_to" search should apply on several fields.
  • Move of artifacts
    • Updated. All the fields assigned to "Contributor" should be moved.
  • Scrum Carwall "Assigned to" display and select
    • Excluded. As soon as more than 1 field is selected for "Contributor", the "Assigned section" is no longer displayed on cards (as if there was no Contributor semantic defined)
    • Reason
      • it's not possible to keep only one field on the card that would group all fields
      • it's not possible to list all possible fields on the card with current implementation. Would need an upgrade of the cardwall to vuejs + burning parrot (as kanban) first.
  • Tracker permission "XXXX have access to artifacts assigned to group"
    • Excluded: as soon as more than 1 field is selected for "Contributor", this permission can no longer be selected in configuration section
    • Reasons
      • Due to the implementation of the permission check the performance penalty would be too high
      • This should be covered by art ... (introduce new permission "XXXX have access to artifacts that are assigned to them")
Empty
Geoffroy Grelot (ggrelot)
Status
Empty
Canceled
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
#12974
Manuel Vacelet (vaceletm)
2019-04-08 11:35
2019-02-07 11:19
4059

References
Artifact links
Empty
Referencing story #12974

Artifact Tracker v5

story #12975 restrict permission to artifact that are assigned to Contributors
epic #13190 Automated "Contributor" semantic
Display settings

Follow-ups

User avatar
Manuel Vacelet (vaceletm)2019-04-08 11:35

Initial proposal didn't meet expectations, see parent epic.

  • So that
    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
  • 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 Canceled
  • Category set to