Project

General

Profile

Actions
Copy link

Bug #414

open

Calculating with key/value fields position number is inconsistent

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

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

70%

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 (0 open — 1 closed)

Copied from Redmine Computable Custom Field - Bug #413: Calculating with key/value fields position number is inconsistentClosedliaham07/12/2021

Actions
Actions
Copy link
 #1

Updated by liaham almost 4 years ago

  • Copied from Bug #413: Calculating with key/value fields position number is inconsistent added
Actions
Copy link
 #2

Updated by liaham almost 4 years ago

  • % Done changed from 100 to 0
Actions
Copy link
 #3

Updated by liaham almost 4 years ago

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.

Actions
Copy link
 #4

Updated by liaham almost 4 years ago

  • % Done changed from 0 to 70

The Redmine issue is confirmed.

Actions
Copy link
 #5

Updated by liaham over 3 years ago

  • Status changed from New to Feedback
Actions
Copy link

Also available in: Atom PDF