Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-8577

Moving an issue from a project to another project means customers in the portal cannot comment on the issue until its type is fixed

      Issue Summary

      Moving an issue from a project to another project means customers in the portal cannot comment on the issue until its request type is fixed

      Steps to Reproduce

      1. Go into agent view and move an issue to a classic project
      2. User comments on the issue on the portal
      3. They get an error when commenting

      Expected Results

      The customer should be able to comment in the portal.

      Actual Results

      They cannot comment.

      Workaround

      Add a type to the issue and the customer can now comment in the portal.

            [JSDCLOUD-8577] Moving an issue from a project to another project means customers in the portal cannot comment on the issue until its type is fixed

            Nicole added a comment -
            Atlassian Update - November 4, 2020

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Desk users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Service Desk Cloud team

            Nicole added a comment - Atlassian Update - November 4, 2020 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Desk users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Service Desk Cloud team

              rcrossman@atlassian.com Rachel Crossman (Inactive)
              shodge@atlassian.com Sebastian Hodge (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: