[Jira] Add configurations for default project

[UXnomaan]

Extension

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

Description

I'd like to have control over what project is set as default when I create an issue. Being part of a big company means you will have a dozen of projects to select from but for majority of your use, you will need to create an issue in your own team's project. This will help speed up issue creation.

This will help with search functionality as well.

Who will benefit from this feature?

Any one that has more than 1 projects in their jira instance.

Anything else?

No response

[raycastbot]

Thank you for opening this issue!

🔔 @thomaslombart @FezVrasta @jesperorb @teziovsky @gavinroderick @gavinroderick @michael-par @literallyjustroy @mheidinger @mikybars @luarmr 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.
• @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

[jfkisafk]

Hey @UXnomaan , Jira already caches the last project used during issue creation:

https://github.com/raycast/extensions/blob/63ed284e297dbbf9012e384d7829d96b47c9eb24/extensions/jira/src/components/CreateIssueForm.tsx#L146-L148

Also, it caches the last project you select from dropdown in search issues as well:

https://github.com/raycast/extensions/blob/63ed284e297dbbf9012e384d7829d96b47c9eb24/extensions/jira/src/search-issues.tsx#L81

Are these features not working for you? Or do you want a preference that you can configure at the extension level to provide a default projectId, so that creation form and search issue dropdown always start from that project?

[UXnomaan]

That works for me, however, I am suggesting a global setting to apply to all of the jira commands that is somewhat permanent as opposed to a cache that can be invalidated.

[jfkisafk]

That works for me, however, I am suggesting a global setting to apply to all of the jira commands that is somewhat permanent as opposed to a cache that can be invalidated.

Thanks for the clarity, so a global preference is what you're looking for. Keep in mind at that level we can't pull all available projects and you'd need to know the projectId for your default project you need to input.

[UXnomaan]

Yes, I expect this to be somewhere in the extension menu and something you define when you are setting up the command.

[thomaslombart]

Hey @UXnomaan, it's unfortunately not possible as preferences are preset (defined statically in the package.json). I'll close out this issue to keep the backlog clean 🙂

[UXnomaan]

Thanks for the explanation @thomaslombart!