ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-10902) Have a status on agreement records
Date Wed, 03 Apr 2019 06:30:03 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-10902?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808406#comment-16808406
] 

Pierre Smits commented on OFBIZ-10902:
--------------------------------------

I experienced this anomaly while working on an r16.11. 

Stating the affected version where the issue first appeared helps existing adopters to determine
whether their implementation is affected.

It does not - per community consensus - imply that a solution suggested (in the form of patch
files) MUST be committed in each affected branch by a committer. Yet, another committer -
again per the community consensus - MAY choose to commit the patch to any of the branches
under support.

> Have a status on agreement records
> ----------------------------------
>
>                 Key: OFBIZ-10902
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10902
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>    Affects Versions: Release Branch 16.11, Release Branch 17.12, Release Branch 18.12
>            Reporter: Pierre Smits
>            Priority: Major
>
> Currently, unlike many other entities, the Agreement entity does not have the statusId
field defined. Agreements, like the other entities, should have a status (values that help
determine the phase of the lifespan beyond the start- and end date of the agreement), such
as:
>  * Created
>  * In Progress
>  * Approved
>  * etc.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message