When absence is concluded, update end date

[supremefist]

No description provided.

[TRyujin]

Is it possible to implement this automation? It's becoming common that we can't set a new absence because concluded absence ends after the new absence begins.

[supremefist]

Will do asap!

…

On Tue, Dec 5, 2017 at 11:45 AM, TRyujin ***@***.***> wrote: Is it possible to implement this automation? It's becoming common that we can't set a new absence because concluded absence ends after the new absence begins. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#79 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB-VQH1jW_Bb9XL7O7dOBnJNryEuOe84ks5s9RDXgaJpZM4J8hcW> .

[supremefist]

Are you sure it is not better to just edit the concluded absence to end on the specific date required? E.g. the current date? Otherwise, there is no way to distinguish between someone editing the end date of a concluded absence and someone concluding an absence for which the end date should be updated automatically.

[TRyujin]

Afaik currently we can't edit concluded absences (not sure if we can edit non-concluded either), so what happens is that absence is concluded earlier of it's end date, but original end date still stays.

[CNTODachi]

You can edit both have just done so on the roster.

[Abuk007]

Can we have it so when you conclude the absence it sets current date as end date? This would sort it out.

[supremefist]

@Abuk007 This is what I'm saying - what's the difference then between editing the end date and concluding an absence (also editing the end date). Also, what if you conclude an absence long after it ended?

[Abuk007]

If from calculational perspective there's no difference, then "conclude" should just edit end date.

From perspective of people managing end users - its single click to end absence - versus editing, opening a calendar and selecting current date and saving.

[supremefist]

There is a big difference, as we don't remain on the date that the absence really concluded for very long (24h). At the moment you have full freedom to create, edit and remove past, future or present absences (concluded or not). You will have to sacrifice this freedom if you want the end date to always be on the date that the absence is physically concluded on the roster.

[Abuk007]

Not sure I understand the technicality behind those limitations.

Could you explain what's the difference between "concluded" and past "end date"?
(Does "concluded" status act as some sort of indicator/flag for calculations?)

How does concluding limit possibilities to edit?

[supremefist]

Good question! The same process is used for both editing absences and concluding absences. That being: editing absences.

…

On 18 Jan 2018 20:17, "Abuk007" ***@***.***> wrote: Not sure I understand the technicality behind those limitations. Could you explain what's the difference between "concluded" and past "end date"? (Does "concluded" status act as some sort of indicator/flag for calculations?) How does concluding limit possibilities to edit? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#79 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB-VQLcQmBe2lnZmHs5YmHqd9LnBc2ouks5tL4rJgaJpZM4J8hcW> .