Defect #12953

Cannot close issues under certain situations

Added by Fred Leeflang almost 9 years ago. Updated almost 9 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues permissions
Target version:-
Resolution: Affected version:2.2.2

Description

Mysql: 5.5.29-0ubuntu0.12.04.1
Environment:
Redmine version 2.2.2.stable.11258
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.11
Environment production
Database adapter MySQL
Redmine plugins:
redmine_scm 0.4.1

As a redmine administrator with all permissions in the workflow (nor as any other user that should be allowed) I cant close certain issues that are in a resolved state.

This does not apply to all issues, I have not been able to narrow down why one issue works but another one doesn't.

This morning I have:

  • updated redmine from svn
  • rake db:migrate RAILS_ENV=production
  • rake redmine:plugins:migrate RAILS_ENV=production (Migrating redmine_scm (SCM Creator)...)
  • restarted Redmine

This has not fixed the problem. Please let me know what other information I need to specify to help fix this.

History

#1 Updated by Daniel Felix almost 9 years ago

Can you define what you've tried?
What do you mean with "cannot close"? You set a ticket to close, but it gets rejected or you haven't the item in your pulldownmenu?

Is the workflow definition set to allow you to close an issue?

#2 Updated by Fred Leeflang almost 9 years ago

Yes, hence 'As a redmine administrator with all permissions in the workflow'.

I don't have 'close' in the issue update pulldown. I have tried with several logins, all of which should have permission to go from Resolved -> Closed. Furthermore I have tried to change different issue fields to see if somehow this prevented 'Closed' from showing up in the pulldown but without any result.

I have also verified that other issues which appear virtually identical (eg. 'Resolved', same Issue Type, same creator, same assigned etc.) can in fact be closed, so this seems like a one-off bug. I'm not sure how many issues this applies to right now in our database but I've asked colleagues to report any they see. So far I have only one that I can clearly reproduce.

#3 Updated by Daniel Felix almost 9 years ago

Is this issue a parent task of some other issue?

#4 Updated by Fred Leeflang almost 9 years ago

Indeed, it has a blocking issue that's still in 'Accepted'. Is this embedded in Redmine right now that the parent task cannot be closed then?

#5 Updated by Daniel Felix almost 9 years ago

Well if you have a task which is blocked by another task, the blocked task can't be closed. :-)

#6 Updated by Fred Leeflang almost 9 years ago

  • Status changed from New to Resolved

Thanks Felix, I've put this on resolved.

#7 Updated by Daniel Felix almost 9 years ago

  • Status changed from Resolved to Closed

So close... ;-)
Daniel...

Thanks for the feedback, I'm closing this one.

#8 Updated by Mischa The Evil almost 9 years ago

FWIW: basically documented in RedmineIssues.

Also available in: Atom PDF