You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Suraj Khurana (JIRA)" <ji...@apache.org> on 2017/09/23 05:05:00 UTC

[jira] [Assigned] (OFBIZ-9625) Improvements in work effort calendar

     [ https://issues.apache.org/jira/browse/OFBIZ-9625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suraj Khurana reassigned OFBIZ-9625:
------------------------------------

    Assignee: Suraj Khurana

> Improvements in work effort calendar
> ------------------------------------
>
>                 Key: OFBIZ-9625
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9625
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: workeffort
>    Affects Versions: Trunk
>            Reporter: Suraj Khurana
>            Assignee: Suraj Khurana
>
> As per communication on dev list:
> Current implementation is we are using enumeration for calendar types and user can't add new calendar types as per own requirements (like holiday calendar, training calendar, meeting calendar etc.)
> Instead of using an enumeration for that, we can use work effort of type CALENDAR and associate it with calendar events as work effort assoc.
> Benefits:
> * User can create a personalized calendar.
> * Same event can be associated with multiple calendars.
> * Enumerations are hard-coded as of now, after this, the method to fetch calendar events will become generic and this improves the beauty of code base and it is not so good as of now.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)