[Jira] Error management can be improved

[Raul Martin]

Extension

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

Description

I'm unable to create an issue after fill of the form (I did before successfully ), likely due to something tied to my workflow in Jira. However, I'm unsure about the specific problem because the information I'm receiving is limited. Failed creating issue
It will be great to be able to see the response from the server.

Who will benefit from this feature?

Every user?

Anything else?

Observe that the app is functioning well. I can view my tasks and the entire sprints and filters. Actually, the app is very impressive.

[raycastbot]

Thank you for opening this issue!

🔔 @thomaslombart @FezVrasta @jesperorb @teziovsky @gavinroderick @gavinroderick @michael-par @literallyjustroy @mheidinger @mikybars you might want to have a look.

💡 Author and Contributors commands

The author and contributors of raycast/jira can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopens the issue.
• @raycastbot assign me Assigns yourself to the issue.
• @raycastbot good first issue Adds the "Good first issue" label to the issue.

[Thomas Lombart]

Could you share a recording? It'll make it easier to see what's happening.

[Raul Martin]

Absolutely, I'm not certain about the situation that I encountered when I first identified the issue, but while attempting to recreate it and record the process, I noticed something.

Some fields are recognized as mandatory, yet others are not. I investigate a little further and looks like the elements are not being mark as mandatory are the custom fields.

I drop here an example from the API, this field is in used in the screen recording.

                        "fieldId": "customfield_xxxxx",
                        "name": "Environment",
                        "type": "com.atlassian.jira.plugin.system.customfieldtypes:select",
                        "description": "The environment where the bug was discovered.",
                        "fieldConfig": {
                            "isRequired": true,
                            "isEditable": true,
                            "nonEditableReason": null,
                            "__typename": "JiraFieldConfig"
                        },

In the screenshot, I purposely created an error to see the "required field" message. I filled in that field and tried to re-submit the issue. However, it failed again. This time, there was no warning or error near any field, nor did the window shake.

I filled in the fields, without guidance from the app, that I knew were necessary.

Afterwards, the ticket was created.

[Thomas Lombart]

Indeed! Something is likely missing here. Do you want to take a look at it? 🙂

[Raul Martin]

@thomaslombart, I think you're correct.

All we need to do is add 'required' parameter. I noticed yesterday that it already exists in the 'customFields'. Probably, we should add 'FormValidation.Required' there. I've seen this in other extensions in the repository.

I'll do that as soon and have time to test it out.