The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources
  • Community
  • Q&A
  • Jira
  • Questions
  • After changing to GreenHopper simplified workflow, manual resolve of issues leaves them in resolution type "Unresolved" which keeps them in a lot of standard views

After changing to GreenHopper simplified workflow, manual resolve of issues leaves them in resolution type "Unresolved" which keeps them in a lot of standard views

Mads Nissen
Mads Nissen
February 28, 2013

As the default simplified workflow does not set the resolution type flag, Resolved issues have resolution type Unresolved. This is not possible to alter manually without changing the workflow back to the default, and then re-resolving the issues in bulk.

Please advice as this is creating a LOT of cruft in our system.

Watch
Like Be the first to like this
369 views

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Teck-En
Teck-En
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 28, 2013

Hi Mads,

It's actually caused by this bug and we have a KB article which provide a workaround: https://confluence.atlassian.com/display/GHKB/Unable+to+set+issues+to+Resolved+using+Greenhopper+Simplified+Workflow

Reply
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security