If Modify Reporter permission is removed for some roles on a project it should not get displayed as a warning.

      This is a valid case where may want to remove the Raise this request on behalf of field from the customer portal for agents.

      My thinking is that a preferred solution is to continue displaying a warning to admins for permissions that are recommended but not mandatory, but allow them to be ignored on a per-user basis and then not shown again unless the warnings change, so they can again be acted on or ignored.

        1. Screen Shot 10-06-15 001.JPG
          Screen Shot 10-06-15 001.JPG
          249 kB
        2. Screen Shot 2015-06-17 at 8.43.15 AM.png
          Screen Shot 2015-06-17 at 8.43.15 AM.png
          97 kB
        3. warning.png
          warning.png
          62 kB

          Form Name

            [JSDSERVER-1969] Warning Alerts for permission scheme should be dismissable

            Hi hailin.zhang,
            Could you create a support ticket at https://support.atlassian.com?
            That way we can provide you with support specific to your circumstances and with higher security.
            The credentials should be the same as for this site (https://jira.atlassian.com).
            Thanks,
            JIRA Service Desk Team

            Marty (Inactive) added a comment - Hi hailin.zhang , Could you create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. The credentials should be the same as for this site ( https://jira.atlassian.com ). Thanks, JIRA Service Desk Team

            Hey Mat,

            Has this issue been fixed in JDS 2.5.2, 2.6.0? We are using JSD 3.0.1 and still can see the warning.

            Cheers
            Hailin

            Hailin Zhang added a comment - Hey Mat, Has this issue been fixed in JDS 2.5.2, 2.6.0? We are using JSD 3.0.1 and still can see the warning. Cheers Hailin

            Evangelos Vrocharis added a comment - - edited

            -Hi Matt,

            Has this been implemented only for the yellow warnings which are believe are for missing recommended permissions?

            Because when there are some extra permissions given the warning is red and there is no dismiss option which is very disappointing. Is this intended? In this case this hasn't fixed anything for us-

            Ignore

            Evangelos Vrocharis added a comment - - edited - Hi Matt, Has this been implemented only for the yellow warnings which are believe are for missing recommended permissions? Because when there are some extra permissions given the warning is red and there is no dismiss option which is very disappointing. Is this intended? In this case this hasn't fixed anything for us - Ignore

            I just raised JSD-3657.

            Matt

            Matthew McMahon (Inactive) added a comment - I just raised JSD-3657 . Matt

            Hi Matt
            No need to bring to anyone's attention as it's very low priority, but if they decide to review the way it works in the future, my suggestion would be not to display the error message if the user becomes an admin AFTER the date the permission scheme was last changed.
            Thanks
            Vikki

            Vikki Short added a comment - Hi Matt No need to bring to anyone's attention as it's very low priority, but if they decide to review the way it works in the future, my suggestion would be not to display the error message if the user becomes an admin AFTER the date the permission scheme was last changed. Thanks Vikki

            Hi Vikki

            Please add any suggestions for how else you would consider handling this, so it can be bought to the attention of our Product Managers for future consideration.

            Regards
            Matt

            Matthew McMahon (Inactive) added a comment - Hi Vikki Please add any suggestions for how else you would consider handling this, so it can be bought to the attention of our Product Managers for future consideration. Regards Matt

            Thanks Matt.
            I can understand the logic behind wanting all admins to see the message, although I can foresee it causing problems when new admins are added in the future, but we'll wait and see!

            Vikki Short added a comment - Thanks Matt. I can understand the logic behind wanting all admins to see the message, although I can foresee it causing problems when new admins are added in the future, but we'll wait and see!

            Hi

            Yes, all administrators should make the choice between fix and dismiss. This also means that if someone changes the permission scheme, then all will become aware and can act upon it.

            Matt

            Matthew McMahon (Inactive) added a comment - Hi Yes, all administrators should make the choice between fix and dismiss. This also means that if someone changes the permission scheme, then all will become aware and can act upon it. Matt

            Vikki Short added a comment - - edited

            Hi Matthew
            Is it right that ALL jira-administrators have to dismiss the warning?
            I'd have thought that the message would disappear for other jira-administrators when one of them dismisses the warning?
            If this is the way it works, then what would happen if all jira-administrators have dismissed the warning and then months down the line a new user is added as an administrator? Would that user have to dismiss the warning message too (i.e. do we need to remember to tell all new jira-administrators to dismiss this message?)
            Thanks
            Vikki

            Vikki Short added a comment - - edited Hi Matthew Is it right that ALL jira-administrators have to dismiss the warning? I'd have thought that the message would disappear for other jira-administrators when one of them dismisses the warning? If this is the way it works, then what would happen if all jira-administrators have dismissed the warning and then months down the line a new user is added as an administrator? Would that user have to dismiss the warning message too (i.e. do we need to remember to tell all new jira-administrators to dismiss this message?) Thanks Vikki

            Hi andy.holvoet

            I understand that you are currently discussing this on a support case. That is still the best course of action.

            Regards
            Matt
            JIRA Service Desk developer

            Matthew McMahon (Inactive) added a comment - Hi andy.holvoet I understand that you are currently discussing this on a support case. That is still the best course of action. Regards Matt JIRA Service Desk developer

            Hi liyong.liu@easesolutions.com

            It is not possible to hide the dialog forever, should permissions change again.

            However, I would recommend opening a new Feature Suggestion ticket on this project, so that the idea can be bought to the attention of our Product Managers for future consideration.

            Regards
            Matt
            JIRA Service Desk developer

            Matthew McMahon (Inactive) added a comment - Hi liyong.liu@easesolutions.com It is not possible to hide the dialog forever, should permissions change again. However, I would recommend opening a new Feature Suggestion ticket on this project, so that the idea can be bought to the attention of our Product Managers for future consideration. Regards Matt JIRA Service Desk developer

            aholvoet added a comment -

            Issue was reintroduced again in version 3.1.1

            Please reopen this ticket.

            aholvoet added a comment - Issue was reintroduced again in version 3.1.1 Please reopen this ticket.

            Hi,
            is there any way to hide or set to "do not remind again" for the error alert as well?
            Thanks
            Leon

            Leon Liu (ease solutions) added a comment - Hi, is there any way to hide or set to "do not remind again" for the error alert as well? Thanks Leon

            This is great, thanks for the update Matt.

            Aggelos Paraskevopoulos [Relational] added a comment - This is great, thanks for the update Matt.

            Hi angel6

            Yes, the fix for this issue is going to be general.

            Basically, the intention is that for Warnings such as Modify Reporter and Delete Issues, administrators will have the option to Upgrade the Permission scheme (as current) or dismiss the warning alert. If the alert includes a critical missing permission, it will not be possible to dismiss.

            Non-Admins will not see any Warnings, as it is up to the administrators to determine if this is desired or not. They will however see critical alerts, to ensure as many people as possible remain with eyes on the issue.

            Regards
            Matt

            Matthew McMahon (Inactive) added a comment - Hi angel6 Yes, the fix for this issue is going to be general. Basically, the intention is that for Warnings such as Modify Reporter and Delete Issues, administrators will have the option to Upgrade the Permission scheme (as current) or dismiss the warning alert. If the alert includes a critical missing permission, it will not be possible to dismiss. Non-Admins will not see any Warnings, as it is up to the administrators to determine if this is desired or not. They will however see critical alerts, to ensure as many people as possible remain with eyes on the issue. Regards Matt

            Hi Matt,

            is the fix going to address also the error for "Delete Issue" permission?

            Cheers,
            Aggelos

            Aggelos Paraskevopoulos [Relational] added a comment - Hi Matt, is the fix going to address also the error for "Delete Issue" permission? Cheers, Aggelos

            On a similar fashion, we get a permission scheme error when removing "Service Desk Agents" from the "Delete Issue" Permission, which seems to us very restrictive.

            Initially reported here.

            Cheers,
            Aggelos

            Aggelos Paraskevopoulos [Relational] added a comment - On a similar fashion, we get a permission scheme error when removing "Service Desk Agents" from the "Delete Issue" Permission, which seems to us very restrictive. Initially reported here . Cheers, Aggelos

            Hi oliviu.nita

            Thanks for the information. It does appear that this is a false warning, as while it is recommended to have the Modify Reporter permission, if you do not, everything is still fine.

            Please watch this ticket for updates, as to when work will start and finish on this issue.

            Regards
            Matt

            Matthew McMahon (Inactive) added a comment - Hi oliviu.nita Thanks for the information. It does appear that this is a false warning, as while it is recommended to have the Modify Reporter permission, if you do not, everything is still fine. Please watch this ticket for updates, as to when work will start and finish on this issue. Regards Matt

            Oliviu Nita added a comment - - edited

            Hi,

            I have disabled the Modify Reporter reporter ONLY for Service Desk Customers - Portal Access -> the error message appears only on the Administration/Agent Side.
            The message are in french but you'ill get the point, see the screen shot.
            The translation is:
            Problems were detected. You must treat them.
            Error authorization system
            The configuration of the authorization of this assistance has errors that affect some features of the helpdesk . We recommend that you upgrade your licensing system to address this problem . The upgrade will copy your existing system and configure permissions requisites.See More
            Hide details
            The security type of Service Desk Customers - Portal Access should be attributed to :
            Modify reporter.*

            Oliviu Nita added a comment - - edited Hi, I have disabled the Modify Reporter reporter ONLY for Service Desk Customers - Portal Access -> the error message appears only on the Administration/Agent Side. The message are in french but you'ill get the point, see the screen shot. The translation is: Problems were detected. You must treat them. Error authorization system The configuration of the authorization of this assistance has errors that affect some features of the helpdesk . We recommend that you upgrade your licensing system to address this problem . The upgrade will copy your existing system and configure permissions requisites.See More Hide details The security type of Service Desk Customers - Portal Access should be attributed to : Modify reporter.*

              mmcmahon Matthew McMahon (Inactive)
              mmcmahon Matthew McMahon (Inactive)
              Affected customers:
              8 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: