-
Bug
-
Resolution: Low Engagement
-
Medium (View bug fix roadmap)
-
None
-
None
-
2
-
Severity 2 - Major
-
3
-
Steps to repro:
1. Setup JIRA and FeCru and applink the two of them
2. Create an issue, and a review.
3. Put a No open reviews condition in the workflow.
4. Put the issue key in the objectives portion of the review.
Expected
You can transition the issue since this field in Crucible has nothing to do with the Development Panel and since the Crucible data isn't reflected in JIRA it should not have an effect on the workflow.
Actual
The transition is not available.
- was cloned as
-
FE-5751 No open reviews condition incorrectly checks Crucible's "Objectives" field for issue key
-
- Closed
-
Form Name |
---|
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center