-
-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CRM-21189 - Add permission for Close and reopen Batch #10983
Conversation
So on this there are 3 aspects
|
In regards to 3 especially, i would recommend setting a preUpgradeMessage for this along the lines of what we did for the changes to sql imports. For reference see here https://github.com/civicrm/civicrm-core/blob/master/CRM/Upgrade/Incremental/php/FourSeven.php#L63 |
27580b3
to
56bb7a7
Compare
@seamuslee001 @eileenmcnaughton thanks a lot for your feedback :) For 3, I have added the preUpgrade message looks for these four permissions: For 2, I am having trouble in finding the right place to document these changes in https://github.com/civicrm/civicrm-dev-docs , is there any section to enlist permissions? |
@monishdeb when in doubt about docs ping @seanmadsen ... :-) |
Note it seems to me from the code that there is an actual change required by the site owner? |
My thinking would be is that it might actually be in the User docs or Sys Admin docs perse |
Thanks for the ping. Here's the relevant area of our docs: https://wiki.civicrm.org/confluence/display/CRMDOC/Default+Permissions+and+Roles I'm currently working on migrating these docs into the Sysadmin Guide, but please feel free to make edits in the mean time. My migration process is script-based and relatively atomic. Soon that wiki page will redirect you to the new Sysadmin Guide! Until then, edit away, and any changes you make will be scooped up by my script. |
56bb7a7
to
ddbdb97
Compare
@seanmadsen yes those 4 new permissions have their description: On otherhand, these four permissions that are responsible to control the batch actions against batch listing are added along with three other batch permissions under 'Notes on Special Permissions' section https://wiki.civicrm.org/confluence/display/CRMDOC/Default+Permissions+and+Roles . |
Thanks @monishdeb Regarding documentation only, I think this this PR is in good shape ✅ |
Cool :) @eileenmcnaughton @seamuslee001 is there anything else I need to address or is it good enough to merge? |
Final Changes look fine to me. If @seanmadsen is happy on the documentation front I am happy also |
@eileenmcnaughton can you merge this PR? |
@monishdeb @seamuslee001 my concern is just that I think we are not being quite explicit enough about what action a site admin would need to take. I feel like they might need to grant an additional permission or some users might lose the ability to do something they were previously able to do? |
@eileenmcnaughton in my opinion after the 4.7.26 upgrade/install, these new permissions doesn't affect admin user. However, it might affect other users with authenticated role and for that purpose, we are providing an indication via preUpgrade message about this change. Further we have a documentation https://wiki.civicrm.org/confluence/display/CRMDOC/Default+Permissions+and+Roles |
@monishdeb Yep - I'm happy with the concept of putting the note in the preUpgradeMessage - but I just feel it needs to be a bit clearer in terms of something like "If you use batches you may need to assign permission y to ensure users can still do x - with a link to the documentation |
---------------------------------------- * CRM-21189: Add permission for Close and reopen Batch https://issues.civicrm.org/jira/browse/CRM-21189
---------------------------------------- * CRM-21189: Add permission for Close and reopen Batch https://issues.civicrm.org/jira/browse/CRM-21189
ddbdb97
to
5ad18cc
Compare
@eileenmcnaughton I have changed the preUpgrade message. Here how it looks now |
I think that does it. |
Yayee. Thanks a lot, @eileenmcnaughton @seanmadsen @seamuslee001 for your feedback :) |
Fail is unrelated - some temporary issue |
Overview
This PR adds 4 new permission for Batches as mentioned in issue CRM-21189
NOTE for release notes - may require a permission tweak for batch users