Project

General

Profile

Actions
Copy link

Bug #413

closed

Calculating with key/value fields position number is inconsistent

Added by liaham over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
liaham
Target version:
3.0.1
Start date:
07/12/2021
Due date:
% Done:

100%

Estimated time:
Affected Version:
Compatible Redmine Version:
Pull Request Link:

Description

The min position number is either 0 or 1 depending on how the corresponding item is created. This leads to unexpected behaviour in calculations.

Related issues 1 (1 open — 0 closed)

Copied to Redmine - Bug #414: Calculating with key/value fields position number is inconsistentFeedbackliaham07/12/2021

Actions
Actions
Copy link
 #1

Updated by liaham over 3 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20
Actions
Copy link
 #2

Updated by liaham over 3 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 20 to 100

The main reason for the observed behaviour could be found in the index view of custom field enumerations. Thus the bug is on Redmine side. This is the issue opend on redmine.org by me.

Until the patch is applied it has to be included in the build.

Actions
Copy link
 #3

Updated by liaham over 3 years ago

  • Assignee set to liaham
Actions
Copy link
 #4

Updated by liaham over 3 years ago

  • Copied to Bug #414: Calculating with key/value fields position number is inconsistent added
Actions
Copy link
 #5

Updated by liaham over 3 years ago

  • Target version changed from 3.0.2 to 3.0.1
Actions
Copy link

Also available in: Atom PDF