Project

General

Profile

Actions

Defect #12953

closed

Cannot close issues under certain situations

Defect #12953: Cannot close issues under certain situations

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

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues permissions
Target version:
-
Resolution:
Affected version:

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.

Updated by Daniel Felix almost 14 years ago Actions #1

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?

Updated by Fred Leeflang almost 14 years ago Actions #2

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.

Updated by Daniel Felix almost 14 years ago Actions #3

Is this issue a parent task of some other issue?

Updated by Fred Leeflang almost 14 years ago Actions #4

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?

Updated by Daniel Felix almost 14 years ago Actions #5

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

Updated by Fred Leeflang almost 14 years ago Actions #6

  • Status changed from New to Resolved

Thanks Felix, I've put this on resolved.

Updated by Daniel Felix almost 14 years ago Actions #7

  • Status changed from Resolved to Closed

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

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

Updated by Mischa The Evil almost 14 years ago Actions #8

FWIW: basically documented in RedmineIssues.

Actions

Also available in: PDF Atom