Defect #24546


Unable to edit Workflows (POST limit)

Added by Ewan Makepeace over 7 years ago. Updated over 7 years ago.

Issues workflow
Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected version:


I now have 35 issue statuses in one of my Redmines. Before you criticise this is because I had two and was adding a third completely separate workflows for different trackers:

Trackers Bug, Feature, Support, Design all use a fairly standard development pipeline with 13 steps from design through final acceptance on live server.
Tracker Recruit also has 13 steps from Invite to Interview to Acceptance or Rejection.

My new tracker for Failure Analysis adds 10 new statuses to the list. However when I try to edit the Workflow with "Only display statuses that are used in this tracker" unchecked (so that I can add in my new statuses) I get the following exception:

Request Entity Too Large

The requested resource
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
Apache/2.2.31 (Amazon) Server at Port 443

I guess the grid of 35 x 35  = 1225 posted values is too many for HTTP? I did some research and PHP typically limits to 1000, other servers to other values.

  1. Is there a quick fix - a server setting I can change?
  2. I dont feel I am using Redmine unreasonably here - but the whole Workflow UX becomes almost unmanageable when you have more than 10 or 15 statuses.
Actions #1

Updated by Ewan Makepeace over 7 years ago

Following on from my second comment....

I would recommend that statuses be put in sets and a tracker subscribe to a set of statuses so you only need to work with a subset of the available status values?

The other thing that drives me crazy (while I am on the subject) is moving status items up and down the list using those little up and down arrows. It is cute with a list of 10 but with 35 over two pages it is ridiculous...

  1. Provide a "Sort by Completion %" option to quickly resort
  2. Allow me to work with subsets as previously requested so that I dont have to look at unrelated statuses.
Actions #2

Updated by Anonymous over 7 years ago


Actions #3

Updated by Toshi MARUYAMA over 7 years ago

  • Subject changed from Unable to edit Workflows to Unable to edit Workflows (POST limit)

Also available in: Atom PDF