langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[RFE] Store the account id that created or updated the applications #5188

New Issue
Closed
opened 2026-02-21 18:09:48 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:09:48 -05:00
Owner
Copy Link
Copy Source

Originally created by @kurokobo on GitHub (Aug 23, 2024).

Originally assigned to: @kurokobo on GitHub.

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

My small team and I were developing apps on Dify within a single workspace, and we found that sometimes it was hard to determine who had created or updated specific apps.

It would be useful if the App model could have created_by, updated_at, and updated_by fields in addition to the current created_at.

2. Additional context or comments

There is no need for these new fields to be displayed in the GUI; it is sufficient if they can be retrieved from the response of /api/apps.

Currently, the App only has created_at, but since Dataset has created_by, updated_at, and updated_by fields, I believe adding these fields to App wouldn't be unnatural.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @kurokobo on GitHub (Aug 23, 2024). Originally assigned to: @kurokobo on GitHub. ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. My small team and I were developing apps on Dify within a single workspace, and we found that sometimes it was hard to determine who had created or updated specific apps. It would be useful if the `App` model could have `created_by`, `updated_at`, and `updated_by` fields in addition to the current `created_at`. ### 2. Additional context or comments There is no need for these new fields to be displayed in the GUI; it is sufficient if they can be retrieved from the response of `/api/apps`. Currently, the `App` only has `created_at`, but since `Dataset` has `created_by`, `updated_at`, and `updated_by` fields, I believe adding these fields to `App` wouldn't be unnatural. ### 3. Can you help us with this feature? - [X] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 18:09:48 -05:00
yindo closed this issue 2026-02-21 18:09:48 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#5188
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?