Plugin is hard to use in muli-team environment.

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 666.va_e39b_132a_519

      Summary:

      Items roles should be independent from items pattern assignment.

      Problem:

      -> each team have devops, developers, qa, managers, viewers
      -> each team have separate folder where they work

      Currently to handle all those access rights i need to set:
      -> 5 different rules per team

      Proposal:

      Split item table on two separate ones.
      In the first one we should be able to set role type access rights.
      In the second one there should be option to set rules for patterns

      First table (copy of current one but without pattern)

      Role Creat Replay     Workspace     Update     Configure     Workspace Read     Create     Delete    
      admin      
      developer              
      manager                  
      devops                  
      qa              

      Second table

      Pattern Name Value
      Team A "./TeamA/**"
      Team B "./TeamB/**"
      Team C "./TeamC/Subfolder"

       Output:

      This should create roles with names

      admin(Team A)

      admin(Team B)

      admin(Team C)

      developer(Team A)

      etc...

      Then those roles then can be used during assignment.

            Assignee:
            Markus Winter
            Reporter:
            Bartosz Nowak
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: