Flyspray - The bug killer!

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bug Report
  • Category Backend/Core
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Low
  • Reported Version 1.0-rc
  • Due in Version 1.0
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray - The bug killer!
Opened by Nikos Baris - 12.01.2017
Last edited by peterdd - 23.01.2017

FS#2326 - Roadmap does not show future version

Let’s say you have multiple projects and decide to add a future version to admin → Version list to affect all projects.
When editing a task from a project and select that future version in “Due In Version” the Roadmap does not show the list of that “future version”.

Sorry for my English

Closed by  peterdd
23.01.2017 21:26
Reason for closing:  Fixed in devel
Additional comments about closing:  

main issue is solved, other topics lets discuss separetly.

Project Manager
peterdd commented on 12.01.2017 16:40

Quickfix with a drawback

Replace in scripts/roadmap.php near line 29:

WHERE project_id = ?

with

WHERE (project_id = ? OR project_id=0)

Downside of this fix without further code changes: All other projects now show that global future version in their roadmap views, even if there is not task assigned to that future version.

And the issue raise more questions

  • Mixed ordering of global future version and project future version.

Example:
global future version list_position values: (10,11,12)
project1 future version list_position values: (4,5,6)
project2 future version list_position values: (1,10,100)

milestone ordering for project1: 4,5,6,10,11,12
milestone ordering for project2: 1,10,10 (global or project first?),11,12,100

  • Should we show a global future version (global milestone) in the roadmap if there is no task assigned to it?
  • What are further pro and contra of maintaining global versions compared to maintain versions separately for each project?
Nikos Baris commented on 16.01.2017 08:43
  • Should we show a global future version (global milestone) in the roadmap if there is no task assigned to it?
  • My opinion it is yes! But better to let the user to choose

  • What are further pro and contra of maintaining global versions compared to maintain versions separately for each project?
  • I do not know if I understand the question but ...
    
    If you are admin and try to add a global version which use a same name
    of one/more that used in projects, inform the administrator 
    (for example with a modal/popup) what should be do with two choices. 
    
        1st choice) Ignore the addition of that version as a global. 
        2nd Choice) Use this as the default.
    
    
    Batch work of the 2nd choice in script run in every project
    
        1. Move existing project tasks belongs in the version with the same name 
           that global (change the relation id on db)
        2. Delete from every project that version.
    
    
Project Manager
peterdd commented on 16.01.2017 16:12

I have now added the fix to flyspray master.

Netherless I do not recommend using global versions. Instead prefer managing the version numbers for each project separately.

Nikos Baris commented on 16.01.2017 16:32

Yes I see that commit.

My opinion: Avoid the usage global versions even if Flyspray provides that feature. For instance if you have a global future version 1.0 and you have projects A and B . Now you release project A as 1.0 .
Suddenly you created a conflict: project A 1.0 (current), project B 1.0 (future)

To avoid any conflict between project that uses a global version, when the administrator adds a global version, make a copy of that to every project, also leave the global version in global version section for new projects (if a new project added will be automate create that version in project)

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing