extensions: [Jira] Missing `title` on Open Issues command

Extension

https://www.raycast.com/raycast/jira

Description

Error:

Error: Rendering failed:
Missing required component property "title"

Steps To Reproduce

  1. In Production
  2. Logged in as (me)
  3. Run “Open Issues” or “Watched Issues” command
  4. All good
  5. Create an issue via the “Create Issue” command
  6. Run “Open Issues” or “Watched Issues” command
  7. Receive an error

Screenshot 2023-04-18 at 14 22 08

Current Behaviour

It seems like the API returns an issue with a missing title? But when I open the Jira list in the browser there are no issues without a title. I can’t debug this unfortunately without knowing which issue it involves.

Expected Behaviour

This command used to work. I’m expecting to see a list of issues assigned to me or ones I am watching. This used to work until a couple of days ago. It seems to break after running the “Create Issue” command. If the API returns an issue without a title, maybe it should be filtered out before trying to render the list.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 3
  • Comments: 30

Most upvoted comments

Awesome. I’ll merge that today.

Hey @colinfitzpatrick, I’ve silently pushed a fix to the extension. I’m not sure this will actually fix the behavior as I’m blindly trying to debug that. Could you uninstall and install the extension again and let me know if you still have the issue?

Thank you.

If it’s easier, I recorded by screen (in case I’m doing something incorrectly) https://www.icloud.com/iclouddrive/0782Y19_HTDhnvNzGAANF-HKQ#My_Movie_2

  1. Install Jira Extension
  2. Go to Open Issues (I log in)
  3. I can see Open issues
  4. Create a new issue (this works)
  5. Go to Open Issues, and I get the Missing title error.

Oh gotcha, I just run the Check for Extension Updates and it updates 2 extensions, I thought the Jira is update as well, anyway it works now, Thx!

@thomaslombart Yep, still seeing the issue after the update. I will try to find some time to produce the log like you say.

You’re not the only one who reported this issue so I’ll keep it opened and will try to reproduce it locally 😊