Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-33332

Notification/ Permission Helper does not work with sub-task

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • Permissions

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? See the corresponding bug report.

      Steps to Reproduce:
      Browse to the Notification/ Permission Helper in Adminstration and try to check for an issue which is a sub-task.

      Expected Results:
      The Notification/ Permission Helper should show me results after adding an issue to check if the user will get notifications/ has access to an issue.

      Actual Results:
      After typing the issue, you get the error that the issue does not exist.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

          Form Name

            [JRACLOUD-33332] Notification/ Permission Helper does not work with sub-task

            Cael Metcalfe added a comment -

            I would just like to commend Atlassian on the turn around time in implementing a fix for this bug, we can only hope other outstanding issues will be fixed just as quickly.

            Cael Metcalfe added a comment - I would just like to commend Atlassian on the turn around time in implementing a fix for this bug, we can only hope other outstanding issues will be fixed just as quickly.

            Carlos Miguel Syquia (Inactive) added a comment -

            Updated the permission helper to query the correct endpoint with the correct query string parameter to show subtasks. Work completed and deployed in EVEREST-2947

            Carlos Miguel Syquia (Inactive) added a comment - Updated the permission helper to query the correct endpoint with the correct query string parameter to show subtasks. Work completed and deployed in EVEREST-2947

            Eric Zheng added a comment -
            Atlassian Update – 20 November 2023

            Hi everyone,

            Thank you for your patience and for bringing this issue to our attention. I'm happy to report that we have reviewed the bug report and the team is now working on a fix for the Permission Helper tool.

            As for the Notification Helper Tool, we are currently evaluating some changes to its overall functionality. Due to these planned updates, we will not be addressing the specified sub-task bug for the Notification Helper tool.

            We appreciate your understanding and will keep you informed of any further updates.

            Best regards,
            Eric
            Product Manager, Jira Software

            Eric Zheng added a comment - Atlassian Update – 20 November 2023 Hi everyone, Thank you for your patience and for bringing this issue to our attention. I'm happy to report that we have reviewed the bug report and the team is now working on a fix for the Permission Helper tool. As for the Notification Helper Tool, we are currently evaluating some changes to its overall functionality. Due to these planned updates, we will not be addressing the specified sub-task bug for the Notification Helper tool. We appreciate your understanding and will keep you informed of any further updates. Best regards, Eric Product Manager, Jira Software

            Eric Zheng added a comment -
            Atlassian Update – 19 October 2023

            Hey everyone,

            We appreciate your patience regarding the update on this bug. We want to inform you that we are working on some changes that may impact the admin Notification Helper tool, and would like to explore this further before addressing the described issue.

            To gather valuable insights, we are launching an Early Access Program (EAP), and would like to extend an invitation to all Jira Cloud admins to join our EAP. By participating, you'll have the opportunity to test out the new changes firsthand and provide us with valuable feedback to help shape the final version of this feature.

            For more details and to sign up for the EAP, please refer to our community article.

            We thank you for your continued patience and collaboration as we plan ahead.

            Best regards,

            Eric
            Product Manager, Jira Software

            Eric Zheng added a comment - Atlassian Update – 19 October 2023 Hey everyone, We appreciate your patience regarding the update on this bug. We want to inform you that we are working on some changes that may impact the admin Notification Helper tool , and would like to explore this further before addressing the described issue. To gather valuable insights, we are launching an Early Access Program (EAP), and would like to extend an invitation to all Jira Cloud admins to join our EAP. By participating, you'll have the opportunity to test out the new changes firsthand and provide us with valuable feedback to help shape the final version of this feature. For more details and to sign up for the EAP, please refer to our community article . We thank you for your continued patience and collaboration as we plan ahead. Best regards, Eric Product Manager, Jira Software

            Cael Metcalfe added a comment -

            +1 this is a hopeless request no doubt, it has been 10 years... ridiculous but par for the course - at least smileys in comments were added within this timeframe, that is a really useful feature.

            Cael Metcalfe added a comment - +1 this is a hopeless request no doubt, it has been 10 years... ridiculous but par for the course - at least smileys in comments were added within this timeframe, that is a really useful feature.

            Ireneusz Kozłowski added a comment -

            As per https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html

             

            I would argue this is above medium because there is no known workaround. And can be as high as highest matching example "administration tools fail"

             

            I would also propose temporary workaround - put warning in permission helper that it doesn't work with sub tasks with recommendation to use parent issue.

            I don't know Jira internal schema, but for user perspective I would say that implementing it in a way where given subtask issue id it autmatically fetches parent id and checks permission there sounds reasonable. This may fail with security levels if/when they are configured differently then parent. - maybe show warning in such cases.

            Ireneusz Kozłowski added a comment - As per https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html   I would argue this is above medium because there is no known workaround. And can be as high as highest matching example "administration tools fail"   I would also propose temporary workaround - put warning in permission helper that it doesn't work with sub tasks with recommendation to use parent issue. I don't know Jira internal schema, but for user perspective I would say that implementing it in a way where given subtask issue id it autmatically fetches parent id and checks permission there sounds reasonable. This may fail with security levels if/when they are configured differently then parent. - maybe show warning in such cases.

            tim.becker added a comment -

            I ran into this problem today. It is really annoying that the permission helper does not work for subtasks.

            We break our work down into small pieces that are assigned to multiple people. If there is an issue with permissions, it is really hard to track down.

            It's even unclear to me, in terms of https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html's bug policy, why this bug has a "low" priority. There is no workaround. It should be at least "medium" priority.

            tim.becker added a comment - I ran into this problem today. It is really annoying that the permission helper does not work for subtasks. We break our work down into small pieces that are assigned to multiple people. If there is an issue with permissions, it is really hard to track down. It's even unclear to me, in terms of https://confluence.atlassian.com/support/atlassian-cloud-bug-fix-policy-206865884.html's bug policy, why this bug has a "low" priority. There is no workaround. It should be at least "medium" priority.

            Brian Sweet added a comment -

            Nine years later and sub-tasks still don't work with the permissions helper... Makes no sense, considering sub-tasks work like regular tasks / issues...

            Brian Sweet added a comment - Nine years later and sub-tasks still don't work with the permissions helper... Makes no sense, considering sub-tasks work like regular tasks / issues...

            Oleksandr Lytvyn added a comment - - edited

            Hello, when this will be implemented?

            Oleksandr Lytvyn added a comment - - edited Hello, when this will be implemented?

            Erin Quick-Laughlin added a comment -

            I noticed a similar cloud issue https://jira.atlassian.com/browse/JRACLOUD-73701 that was closed but related to this one, regarding the sub-task not showing in the Permissions Helper.  I assume that means Atlassian believes the two issues have the same root cause.

             

            Perhaps this will be resolved when they finish transforming Epics into the new standard of hierarchy items?  https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/ 

            Erin Quick-Laughlin added a comment - I noticed a similar cloud issue https://jira.atlassian.com/browse/JRACLOUD-73701 that was closed but related to this one, regarding the sub-task not showing in the Permissions Helper.  I assume that means Atlassian believes the two issues have the same root cause.   Perhaps this will be resolved when they finish transforming Epics into the new standard of hierarchy items?   https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/  

              jthomas@atlassian.com Justin Thomas
              pcora Pedro Cora
              Affected customers:
              91 This affects my team
              Watchers:
              69 Start watching this issue

                Created:
                Updated:
                Resolved: