Changes between Version 16 and Version 17 of MolgenisTicketFaq


Ignore:
Timestamp:
2010-12-01T10:51:47+01:00 (14 years ago)
Author:
Morris Swertz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MolgenisTicketFaq

    v16 v17  
    5252So what you need to do is describe this expected output.
    5353
    54 Example ticket: '''Comparison of imputation methods Beagle, Impute and MACH'''
     54Example ticket:
    5555
    5656{{{
     57title: Comparison of imputation methods Beagle, Impute and MACH
     58
    5759component: gwas
     60
     61description:
    5862
    5963Why or for whom?
     
    7882An '''enhancement''' is working on a new set of features in our software. In this case we EXPECT that there has already been a ticket that defines this enhancement. In these cases the ticket is simple:
    7983
    80 Example ticket: Implement use case: SearchQTLprofiles
     84Example ticket:
    8185{{{
     86title: Implement use case: SearchQTLprofiles
     87
    8288component: xqtl
    8389
     90description:
    8491Implement the enhancement as described in
    8592
     
    96103A '''defect''' is a known error in our code base. In this case the ticket MUST describe what you need to do to reproduce the defect and you MUST create a test that shows the problem. If possible you will first create a UnitTest that shows the bug so that it can never come back without us knowing.
    97104
    98 Example ticket: Fix JPA if primary key is not named 'id'
     105Example ticket:
    99106{{{
     107title: Fix JPA if primary key is not named 'id'
     108
    100109component: molgenis
     110
     111description:
    101112
    102113Why or for whom?
     
    127138Example ticket:
    128139{{{
     140title: Java REST client doesn't work
     141
     142component: molgenis
     143
     144description:
    129145Why or for whom?
    130146We got a report stating that the REST api doesn't work from Java client