plane icon indicating copy to clipboard operation
plane copied to clipboard

[bug]: Intake Work Item Broken URL

Open leedsjb opened this issue 8 months ago • 3 comments

Is there an existing issue for this?

  • [x] I have searched the existing issues

Current behavior

When I copy an Intake Work Item URL I expect navigating to it to load the specific intake work item. Instead, the first work item in the intake list loads and the URL redirects to the URL for that first item.

The Intake Work Item is open in pending status.

Example URL:

https://<workspace URL>//projects/1466dd80-3b3e-4663-96c8-d8996febba00/inbox/?currentTab=open&inboxIssueId=12307b13-2ca9-47b2-a658-81c6c053dd98

The following error appears in the browser console regardless of whether or not the right Work Item loads.

Image

Steps to reproduce

  1. Open Intake
  2. Select Work Item
  3. Copy URL from nav bar
  4. Open new window
  5. Paste URL

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.8.3

leedsjb avatar Apr 11 '25 20:04 leedsjb

Hi @leedsjb we’ve tried to reproduce the issue on our end, but it appears to be working as expected. You can check the screen recording here https://drive.google.com/file/d/1EerEmnjc8zrJCQ2jprATh20cZSVY9v74/view?usp=sharing. Please let us know if there's anything we might be overlooking. Also, the console error you mentioned is totally unrelated to this issue.

pushya22 avatar Apr 15 '25 08:04 pushya22

Thanks @pushya22 and @sriramveeraghanta . Are you able to try to reproduce in Plane Self-Hosted v1.8.3. Noticed you're using Plane One in the screen recording. This is still occurring in our v1.8.3 install - however I learned more details. It only happens for some Intake Work Items - not all. I can't identify a conclusive reason why some and not others however it typically happens on older items.

leedsjb avatar Apr 23 '25 17:04 leedsjb

Hi @leedsjb The URL indicates one version, but the recording is actually from Plane Self-Hosted v1.8.3. We haven’t been able to reproduce the issue on this version so far, but we’ll dig deeper to check if it might be related to older data.

pushya22 avatar Apr 23 '25 17:04 pushya22

Hi @leedsjb This issue pushed a possible fix in one our recents releases. Closing the issue, but feel free to re-open in case the issue persists.

pushya22 avatar Jul 10 '25 08:07 pushya22

@pushya22 thank you. In 1.12.0?

leedsjb avatar Jul 10 '25 15:07 leedsjb