Hello @Brittany King ,
Thanks for reaching out and welcome to the community!
From your description you noted that you are updating an issue status, I played around with this a bit on various board configurations between the Team managed (Previously Next-gen board) boards and Company Managed (Previously Classic Boards) and the status does update on the board view correctly on an auto-refresh event in my testing after applying a change to the status of the issue in either a separate tab or in the modal pop up from the board view directly. Noting the Project naming convention is rolling out starting today so depending on where you are in the update rollout the naming could be in either state when you are looking at this.
I would be happy to take a look at this more but I need some additional information as I am not seeing the behavior you are noting occur. A screenshot would be really helpful showing the two states.
For some additional context, can you outline the project type (Team managed or Work Managed) and board type (Kanban or scrum) and the steps in the process you are following to recreate the error, i.e. changing the status in another tab from where you are viewing the board, or using a post function or automation rule to apply the change, and what order the actions are being applied?
Next does the status change to reflect the update if you refresh the page while viewing the board, or does the mismatch remain?
I would also recommend applying a few browser troubleshooting steps to see if there is something causing the browser to hold onto the cached details without refreshing, Please try:
- flushing out browser cache
- testing in an alternate browser
- Incognito/private browser mode to disable browser add-ons that could be conflicting
Let me know what you find.
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.