Within workspaces and workflows that are undergoing active group development (eg. rebc-oct16/rebc_template) the implementation of access rules for updated workflows do not consider inheritance from the previous version. This results in repeatedly having to type multiple email addresses for each successive update, which might be ok if we updated workflows once every few months, but in the development process we often make daily or hourly changes and the access lists tend to be a casualty. This inevitably results in workspaces and method repos cluttered with similarly named workflows that are difficult to manage. The situation is so bad that I've been trying bypass the access mess by making everything I do public, but since that is also not inherited from previous versions, more often than not I forget to check the public box. Can we make the default workflow access public or make the default access for a workflow based on the previous version?
↧