You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to figure out how to create a feature for validations where the page will just show unpaid work. There are some ways that would sort of work, like not showing closed processes, or showing events only for one month.
But both of those are not really right, and make everything less flexible.
In terms of closed processes, we would like for processes and plans that actually cross months to be able to do that, it will be much better representation of the actual work, and important when we have processes connected by inputs and outputs.
If we only show the events for one month, then we will exclude the possibility of people getting paid for something from the previous month that slipped through the cracks. And waiting for everything each month just makes it really late for everyone, where if some late things could be skipped until next month, people could get paid on time. And people won't be logging work in the wrong month, which does not help with the date reflecting reality for analysis etc.
The right way to do it is to know what work has been paid. OCP could handle this because when OCP income distributions happen, it records which event(s) are affected by which distribution(s). (It can also handle partial payments, ongoing payments, etc.) I understand that Kispagi saves the distribution data, but it is not connected in any way yet back to the original work events.
Proposal: We need to be able to see what work was paid for. So we need to be able to connect the distribution data from Kispagi to the event data from OCP. (It would also be great to connect it to work data from Gitlab, but we don't need that for this validation feature.) There are a couple ways I can think of that this could happen:
Kispagi could feed distribution data back into OCP and OCP could create the data associating contribution events with distribution events.
Kispagi could save this data and provide an api so that the new validation app could bring in data from both OCP and Kispagi to be able to tell what contributions were paid already.
I like the second one best, seems cleaner; and also gives better possibility to also use this data for analytics and accounting, since it will then include all distributions for all work, from OCP and Gitlab and whatever else is used in the future.
This question is also related to the request to have Kispagi actually do the payments instead of producing a report and the payments done manually. We would want to do that the same way, either from Kispagi (corresponds to 2nd option) or from OCP (corresponds to first option).
The text was updated successfully, but these errors were encountered:
We need to figure out how to create a feature for validations where the page will just show unpaid work. There are some ways that would sort of work, like not showing closed processes, or showing events only for one month.
But both of those are not really right, and make everything less flexible.
The right way to do it is to know what work has been paid. OCP could handle this because when OCP income distributions happen, it records which event(s) are affected by which distribution(s). (It can also handle partial payments, ongoing payments, etc.) I understand that Kispagi saves the distribution data, but it is not connected in any way yet back to the original work events.
Proposal: We need to be able to see what work was paid for. So we need to be able to connect the distribution data from Kispagi to the event data from OCP. (It would also be great to connect it to work data from Gitlab, but we don't need that for this validation feature.) There are a couple ways I can think of that this could happen:
I like the second one best, seems cleaner; and also gives better possibility to also use this data for analytics and accounting, since it will then include all distributions for all work, from OCP and Gitlab and whatever else is used in the future.
This question is also related to the request to have Kispagi actually do the payments instead of producing a report and the payments done manually. We would want to do that the same way, either from Kispagi (corresponds to 2nd option) or from OCP (corresponds to first option).
The text was updated successfully, but these errors were encountered: