issues listed in project board need to be updated after them were moved #6285

New Issue

GiteaMirror · 2025-11-02T06:51:03-06:00

GiteaMirror commented

2025-11-02 06:51:03 -06:00

Originally created by @suli3 on GitHub (Nov 10, 2020).

Gitea version (or commit ref): 1.14.0+dev-12-gcb171dbd5
Git version:2.29.2
Operating system: gitea.com
Database (use [x]):
- PostgreSQL
- [ x] MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- [ x] Yes (provide example URL)
- No
Log gist:

Description

I found that maybe the status/position of the issues listed in project board need to be updated after them were moved.

Screenshots

Set up
move issue1 from To Do, to In Progress
Click into the issue and then back to the project board, the issue1 change back to To Do. It should be still in the In Progress

Originally created by @suli3 on GitHub (Nov 10, 2020).   - Gitea version (or commit ref): 1.14.0+dev-12-gcb171dbd5 - Git version:2.29.2 - Operating system: gitea.com    - Database (use `[x]`): - [ ] PostgreSQL - [ x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ x] Yes (provide example URL) - [ ] No - Log gist:    ## Description I found that maybe the status/position of the issues listed in project board need to be updated after them were moved. ## Screenshots 1. Set up ![)W9{FKQK@@H9Q39 0OLQR%P](https://user-images.githubusercontent.com/1057425/98685691-a54ea180-23a2-11eb-83e1-eb2021e13b68.jpg) 2. move issue1 from To Do, to In Progress ![DTK~C7~}PWM{82DPWYSAO0J](https://user-images.githubusercontent.com/1057425/98685771-beefe900-23a2-11eb-8844-b55540043858.jpg) 3. Click into the issue and then back to the project board, the issue1 change back to To Do. It should be still in the In Progress ![M( L3S %(`NM) %WU $QWT](https://user-images.githubusercontent.com/1057425/98685837-d62ed680-23a2-11eb-9a0e-abd3fb1ad06f.jpg)

GiteaMirror added the topic/projects label 2025-11-02 06:51:03 -06:00

GiteaMirror commented

2025-11-02 06:51:04 -06:00

@POPSuL commented on GitHub (Nov 11, 2020):

I think, programmable issue transition needed, like jira.
Each panel should have option like "ON_DROP_ISSUE" with "programmable" actions, eg:

set label "WIP" if issue dropped to "In Progress"
set label "Need review" and Assign reviewers automatically (or randomly, by predefined list, or better developer by inspect git-blame result in related PR)
discussion should be closed which issue dropped to "Closed"
...
N. more examples?

@POPSuL commented on GitHub (Nov 11, 2020): I think, programmable issue transition needed, like jira. Each panel should have option like "ON_DROP_ISSUE" with "programmable" actions, eg: 1. set label "WIP" if issue dropped to "In Progress" 2. set label "Need review" and Assign reviewers automatically (or randomly, by predefined list, or better developer by inspect git-blame result in related PR) 3. discussion should be closed which issue dropped to "Closed" 4. ... N. more examples?

GiteaMirror commented

2025-11-02 06:51:04 -06:00

@bobemoe commented on GitHub (Nov 28, 2020):

I think the issue reported by @suli3 is a caching issue. I can recreate it here in firefox using the 3 steps described in OP, and I would suggest step 4: refresh the page and see that the issue then appears "In Progress" as is should be.

I don't think the suggestion by @POPSuL would actually help here, however it is a brilliant idea and probably needs its own issue? In fact I thought there was one about changing labels on issues as they are moved around project boards, but I cant find it now :/

@bobemoe commented on GitHub (Nov 28, 2020): I think the issue reported by @suli3 is a caching issue. I can recreate it here in firefox using the 3 steps described in OP, and I would suggest step 4: refresh the page and see that the issue then appears "In Progress" as is should be. I don't think the suggestion by @POPSuL would actually help here, however it is a brilliant idea and probably needs its own issue? In fact I thought there was one about changing labels on issues as they are moved around project boards, but I cant find it now :/

GiteaMirror commented

2025-11-02 06:51:05 -06:00

@bobemoe commented on GitHub (Feb 27, 2021):

I'm still seeing this as a caching issue. Just confirmed in latest 1.14.0+dev-764

@lunny theme/kanban label?

@bobemoe commented on GitHub (Feb 27, 2021): I'm still seeing this as a caching issue. Just confirmed in latest 1.14.0+dev-764 @lunny theme/kanban label?

GiteaMirror commented

2025-11-02 06:51:05 -06:00

@zeripath commented on GitHub (Mar 3, 2021):

The likely issue here is one that the ajax request to update the board of the issue has not completed before you click away and thus the change is cancelled

@zeripath commented on GitHub (Mar 3, 2021): The likely issue here is one that the ajax request to update the board of the issue has not completed before you click away and thus the change is cancelled

GiteaMirror commented

2025-11-02 06:51:05 -06:00

@bobemoe commented on GitHub (Mar 3, 2021):

In my experience of this the change is actually saved as expected. When it's displaying in the wrong column, just refresh the page to see it move to where it should be, see my comment https://github.com/go-gitea/gitea/issues/13498#issuecomment-735253270

I think the issue reported by @suli3 is a caching issue. I can recreate it here in firefox using the 3 steps described in OP, and I would suggest step 4: refresh the page and see that the issue then appears "In Progress" as is should be.

@bobemoe commented on GitHub (Mar 3, 2021): In my experience of this the change *is* actually saved as expected. When it's displaying in the wrong column, just refresh the page to see it move to where it should be, see my comment https://github.com/go-gitea/gitea/issues/13498#issuecomment-735253270 >I think the issue reported by @suli3 is a caching issue. I can recreate it here in firefox using the 3 steps described in OP, and I would suggest step 4: refresh the page and see that the issue then appears "In Progress" as is should be.

GiteaMirror commented

2025-11-02 06:51:05 -06:00

@tobiasBora commented on GitHub (Sep 12, 2022):

See also this related issue https://github.com/go-gitea/gitea/issues/14359

@tobiasBora commented on GitHub (Sep 12, 2022): See also this related issue https://github.com/go-gitea/gitea/issues/14359

GiteaMirror commented

2025-11-02 06:51:06 -06:00

@lunny commented on GitHub (Oct 26, 2025):

This should be a frontend problem. It's not related to #14359 . After moving to another column, a history should be pushed?

@lunny commented on GitHub (Oct 26, 2025): This should be a frontend problem. It's not related to #14359 . After moving to another column, a history should be pushed?

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6285