Project

General

Profile

Actions
Copy link

Defect #20071

closed

User can't update issue status after upgrade

Added by Emmanuel BOUGEROLLE over 9 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues workflow
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:
3.0.3

Description

After a migration to 3.0.3 a user can't update issue status.

Workflow is ok.

Actions
Copy link
 #1

Updated by Toshi MARUYAMA over 9 years ago

  • Status changed from New to Needs feedback
  • Priority changed from Urgent to Normal
Actions
Copy link
 #2

Updated by Toshi MARUYAMA over 9 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to No feedback

No feedback.

Actions
Copy link
 #3

Updated by Emmanuel BOUGEROLLE almost 9 years ago

  • Status changed from Closed to Reopened

Hi,

Sorry for delay.

After a new attempt to migrate redmine 2.1.2.devel to redmine 3.2 i have the same problem.

After migration a reporter can't anymore update status for an issue. It can only update passed time, add comment and activity.

Before migration same user can update status, assigned to, passed time, add comment and activity.

Here environnent informations :

sh: 1: svn: not found
sh: 1: darcs: not found
not trusting file /home/deploy/apps/redmine/.hg/hgrc from untrusted user deploy, group www-data
sh: 1: cvs: not found
sh: 1: bzr: not found
Environment:
Redmine version 3.2.0.devel
Ruby version 2.1.5-p273 (2014-11-13) [x86_64-linux]
Rails version 4.2.5
Environment production
Database adapter Mysql2
SCM:
Mercurial 2.8.2
Git 1.9.1
Filesystem
Redmine plugins:
no plugin installed

Actions
Copy link
 #4

Updated by Toshi MARUYAMA almost 9 years ago

  • Status changed from Reopened to Needs feedback
  • Resolution deleted (No feedback)

Why do you use "3.2.0.devel"?

Actions
Copy link
 #5

Updated by Emmanuel BOUGEROLLE almost 9 years ago

It's an mistake. But I think i've found the problem.

I havent completely read all changelings since 2.1.2.

The edit issue properties was not set in permissions.

In 3.2 version it seems that this permission needs to be set for update status and adapt with field permission.

I have to deepen this question to adapt all the settings

Actions
Copy link
 #6

Updated by Go MAEDA over 3 years ago

  • Status changed from Needs feedback to Closed
  • Resolution set to Invalid

Emmanuel BOUGEROLLE wrote:

It's an mistake. But I think i've found the problem.

I havent completely read all changelings since 2.1.2.

The edit issue properties was not set in permissions.

In 3.2 version it seems that this permission needs to be set for update status and adapt with field permission.

Thank you for the feedback. Closing.

Actions
Copy link

Also available in: Atom PDF