Project

General

Profile

Actions

Defect #13188

closed

Forms are not updated after changing the status field without "Add issues" permission

Added by Akira Nakai about 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
High
Category:
Issues workflow
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

I noticed that after changing the status field, the screen is updated, according to the workflow configuration. However, I noticed that sometimes the screen is not updated as expected. I found out that this behaviour occurs when I am a user that has a role without permission to add new issues.

Example:
1-Consider an issue in "New" status.
2-Log on with a user "John" that has a role unable to create new issues (only update).
3-John changes the issue status to "Analysis".
4-Screen refreshes the group of fields presented to him.
5-Consider that there is a mandatory field to be filled in when the issue status is "Analysis" (not showed in "New" status).
6-However, the screen does not show that mandatory field.

But, if we go to workflow configuration admin page and enable John to add new issues and repeat the previous steps, the mandatory field is there as expected! However, we would not like to enable John to add issues...

Environment:
Redmine version 2.1.2.stable
Ruby version 1.8.7 (x86_64-linux)
Rails version 3.2.8
Environment production
Database adapter MySQL

Actions #1

Updated by Jean-Philippe Lang about 11 years ago

  • Status changed from New to Confirmed
  • Priority changed from Normal to High
Actions #2

Updated by Jean-Philippe Lang about 11 years ago

This was broken long time ago by r4011.

Actions #3

Updated by Jean-Philippe Lang about 11 years ago

  • Subject changed from Forms are not updated after changing the status field to Forms are not updated after changing the status field without "Add issues" permission
  • Status changed from Confirmed to Closed
  • Assignee set to Jean-Philippe Lang
  • Target version set to 2.3.0
  • Resolution set to Fixed

This is fixed in r11405, thanks for pointing this out.

Actions

Also available in: Atom PDF