Jan Skalicky

My feedback

  1. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Jan Skalicky supported this idea  · 
  2. 211 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    Jan Skalicky supported this idea  · 
  3. 447 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  General » Setup/administration  ·  Flag idea as inappropriate…  ·  Admin →
    Jan Skalicky commented  · 

    Or create some other entity (e.g.: "Space" ) to which everything will be scoped. We want to have one Octopus instance for different teams and at this time there is couple of things we fight with.

    This is our scenario:
    We want to have one team which will take care of upgrading Octopus and all needed administration.
    We have multiple teams. Each one wants to have unlimited access to their environments, accounts, tenants, lifecycles, project groups, "sub teams" and "sub roles", variable sets and action templates (these should be common and specific).

    Jan Skalicky commented  · 

    Please scope variable set to project group or project. Everyone with permissions:
    to project group + to edit variables + edit variables sets
    will be able to work with that variable set.

    Jan Skalicky supported this idea  · 

Feedback and Knowledge Base