Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-3956

Error creating subtask when parent issue is closed in Jira

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Reproduce steps :
      The Jira Issue associated with the Crucible Review is closed in Jira.

      • still can click "create issue" from a Review comment in Crucible.
      • receive the error message - Error creating subtask in JIRA - error returned was null - likely a permission/login error.
      • No subtask in created in Jira.

      Error message should be more specified e.g "Error creating subtask in JIRA - Jira issue has a closed status" instead of "Error creating subtask in JIRA - error returned was null - likely a permission/login error. "

            [CRUC-3956] Error creating subtask when parent issue is closed in Jira

            Marek Parfianowicz added a comment -
            Atlassian Update – 31 January 2020

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 31 January 2020 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Development Team Lead

            Trey Hyde added a comment -

            And also perhaps force a reopen?

            Trey Hyde added a comment - And also perhaps force a reopen?

              Unassigned Unassigned
              tlum Tracey Lum [Atlassian]
              Votes:
              8 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: