Changes between Version 1 and Version 2 of Developers/Working On Tickets


Ignore:
Timestamp:
2017-09-19T17:21:56+02:00 (3 years ago)
Author:
clevy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Working On Tickets

    v1 v2  
    2121 
    2222Each expert is requested to check regularly the list of open tickets in order to: 
    23 * accept some assignments which are relevant to his expertise or good will 
    24 * propose assignments for newly created tickets 
     23* [[span(''accept some assignments which are relevant to his expertise or good will'', style=color:lime)]] 
    2524 
    26 In fact, if we intend to have an up-to-date ticketing system, there should be nearly no tickets under "new" status, and each expert should have a few (more than one...) tickets assigned to him. 
     25* [[span(''propose assignments for newly created tickets'', style=color:lime)]] 
    2726 
     27'''In fact, to have an up-to-date ticketing system, there should be nearly no tickets under "new" status, and each expert should have a few (more than one...) tickets assigned to him/her.''' 
    2828 
     29Accepting assignments is indeed important in order to share a clear view on the list of tickets remaining to be taken in account. 
    2930 
     31== Workflow for a given ticket 
     32Once an expert has accepted the assignment, the following items should be completed: 
     33* in the ticket, describe the chosen answer(s) 
     34* if some changes or fixes are to be commited in the NEMO reference, those should be tested before commit, including full SETTE tests in debug mode 
     35* in the comments of commit, do not forget the associated ticket number 
     36* check where commits are relevant (maybe at least 2 places: in the shared users version (3_6_STABLE for now) and in the trunk (version under development) 
     37* when tasks are completed, close the ticket 
    3038 
    3139