View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0020098mantisbtadministrationpublic2015-09-10 15:512015-09-10 17:16
Reportercproensa Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Summary0020098: Changing project specific configuration management applies to current project, not "intended" project
Description

seems like saving settings (eg: manage_config_workflow_set.php) uses current project to store settings, and is evaluated once the form is sent.
If current project has been changed (on another browser tab, etc), settings are applied to that project instead of the one that was intended (and stated) on the administration page

Steps To Reproduce
  • open two browsers (tabs), with same logged in user session
  • on window1, open manage configuration (workflow, thresholds, etc), select project A, and let it open
  • on windows2 open any page and select project B as current project
  • change setting on window 1 and save.
  • settings are applied to project B, instead of project A
Additional Information

Sensible fix may be including affected project id, in the management form, as a hidden field, to be retrieved and used by the form processing

TagsNo tags attached.

Relationships

Relationship GraphDependency Graph
related to 0009193 assignedcommunity "Selected project" state should be client-side not server-side 

Activities

cproensa

cproensa

2015-09-10 15:53

reporter   ~0051440

happens on both 1.3 master and 1.2.19