api/issues: Set custom date #2410

Closed
opened 2025-11-02 04:35:05 -06:00 by GiteaMirror · 8 comments
Owner

Originally created by @mappu on GitHub (Oct 15, 2018).

  • Gitea version (or commit ref): 1.5.2
  • Git version: 2.19
  • Operating system: Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Hi,

I'm writing an importer for Fossil issues to Gitea issues. The Gitea API allows to create and manage issues, but always with the current date only; it can't create an issue or comment using a past date. This means my importer loses some fidelity.

I would like the option, in the API, to specify a custom date when creating or modifying a ticket. Probably this functionality should only be available to administrators (or repo owners).

Originally created by @mappu on GitHub (Oct 15, 2018). - Gitea version (or commit ref): 1.5.2 - Git version: 2.19 - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [X] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description Hi, I'm writing an importer for Fossil issues to Gitea issues. The Gitea API allows to create and manage issues, but always with the current date only; it can't create an issue or comment using a past date. This means my importer loses some fidelity. I would like the option, in the API, to specify a custom date when creating or modifying a ticket. Probably this functionality should only be available to administrators (or repo owners).
GiteaMirror added the issue/confirmedtype/enhancementmodifies/api labels 2025-11-02 04:35:05 -06:00
Author
Owner

@adelowo commented on GitHub (Oct 17, 2018):

Interesting, Github doesn't support a custom date too... https://developer.github.com/v3/issues/#create-an-issue

@adelowo commented on GitHub (Oct 17, 2018): Interesting, Github doesn't support a custom date too... https://developer.github.com/v3/issues/#create-an-issue
Author
Owner

@Dmole commented on GitHub (Oct 21, 2018):

There are laws about date manipulation so probably it would be best to just include "date reported (if differing from issue date)" in a body template.

@Dmole commented on GitHub (Oct 21, 2018): There are laws about date manipulation so probably it would be best to just include "date reported (if differing from issue date)" in a body template.
Author
Owner

@lafriks commented on GitHub (Oct 21, 2018):

It should be in internal API that only administrator should be able to call

@lafriks commented on GitHub (Oct 21, 2018): It should be in internal API that only administrator should be able to call
Author
Owner

@stale[bot] commented on GitHub (Jan 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
Author
Owner

@stale[bot] commented on GitHub (Feb 23, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 23, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.
Author
Owner

@shashvat-kedia commented on GitHub (Mar 17, 2019):

@lafriks Can I work on this?

@shashvat-kedia commented on GitHub (Mar 17, 2019): @lafriks Can I work on this?
Author
Owner

@lunny commented on GitHub (Mar 17, 2019):

@sd1998 Please!

@lunny commented on GitHub (Mar 17, 2019): @sd1998 Please!
Author
Owner

@6543 commented on GitHub (Sep 21, 2020):

I think we should go the way to enhance & integrate things into gitea's own included migration tool instead :)

so I'll close this for now. If really needed ask for reopen it.

@6543 commented on GitHub (Sep 21, 2020): I think we should go the way to enhance & integrate things into gitea's own included migration tool instead :) so I'll close this for now. If really needed ask for reopen it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2410