Skip to content

[17.0][ADD] helpdesk_timesheet_date_time_order: New module helpdesk_t…#766

Closed
lbarry-apsl wants to merge 1 commit into
OCA:17.0from
APSL:17.0-add-helpdesk_timesheet_date_time_order
Closed

[17.0][ADD] helpdesk_timesheet_date_time_order: New module helpdesk_t…#766
lbarry-apsl wants to merge 1 commit into
OCA:17.0from
APSL:17.0-add-helpdesk_timesheet_date_time_order

Conversation

@lbarry-apsl

Copy link
Copy Markdown
Member

Add new to the top of the list, rather than the bottom, and sort by date time
in descending order.

cc https://github.com/APSL #HT02143

@miquelalzanillas @mpascuall @javierobcn @peluko00 @BernatObrador @ppyczko please review

@lbarry-apsl
lbarry-apsl force-pushed the 17.0-add-helpdesk_timesheet_date_time_order branch from d758269 to 4c37ffd Compare June 18, 2025 06:59
@dalonsod

Copy link
Copy Markdown
Contributor

Hello @lbarry-apsl this could be a good improvement for base helpdesk_mgmt_timesheet addon IMO.

Obviously, this functionality would slightly change current behavior, that is a good point for an ADD instead an IMP. At the other side, it's a very small change, that could be adopted without any problem for current helpdesk_mgmt_timesheet users and maintainers, what do you think?

@lbarry-apsl

Copy link
Copy Markdown
Member Author

Hi @dalonsod ,

Very good suggestion, but I think some users prefer the original order. Don't you think so?

@dalonsod

Copy link
Copy Markdown
Contributor

Well, as one of the original authors I'd directly approve such thing as an IMP, but I'm not the only one... we could ask another usual developers. Anyway, feel free to go ahead with this addon.

@lbarry-apsl

Copy link
Copy Markdown
Member Author

Okay, so I'm going to open another PR with these changes to the module helpdesk_mgmt_timesheetas an improvement, to see if there's acceptance.

@github-actions

Copy link
Copy Markdown

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions Bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 19, 2025
@github-actions github-actions Bot closed this Nov 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants