For each Worklog, a status has to be stored.

Possible solutions :

• Use OSProperties library (Like Tempo !!) :
  • Data will not be requested through an OFBiz Complex query
  • It will need request by API : 1 Week of Worklog with 4 Worklog by day = 20 Worklogs ... It may increase the number of request !

• Use the Worklog Type to store approval status :
  • The Worklog Type feature would no more efficient !
  • We hope to see Worklog type integrate in future release of JIRA

• Extend Worklog Type entity by adding new field :
  • Is it acceptable by Atlassian when they will integrate Worklog type

• Use NodeAssocation table which give the ability to linked 2 OFBiz entities :
  • It means to use a large entity (sourceNodId,sourceNodeEntity,sinkNodId,sinkNodeEntity,AssociationType,Sequence) to store 1 attribute !
  • We may then benefit of all the model and provide a history

    sourceNodId	sourceNodeEntity	sinkNodId	sinkNodeEntity	AssociationType	Sequence
    10000	Worklog	TS-1	Issue	RequestApproval	1
    10000	Worklog	TS-1	Issue	validateWorklog	2
    10001	Worklog	TS-1	Issue	RequestApproval	1
    10001	Worklog	TS-1	Issue	unvalidateWorklog	2
    10001	Worklog	TS-1	Issue	RequestApproval	3
    10001	Worklog	TS-1	Issue	unvalidateWorklog	4

COS :

• Storage has to be done in native entity (NO new table has to be created)
• Storage has to be requestable (No storage in OSProperties table)