Allow configuration of Jira branch names

[BehnH]

Description

This allows configuration of Jira git branch names - like is configurable in the Jira web UI. To match Jira's UI, the following options are allow: Issue key ({issueKey}), Issue summary ({issueSummary}), Issue summary short ({issueSummaryShort}), Issue type ({issueType}), and Project key ({projectKey}).

The default behavior is for the extension to behave as it does today (Issue key followed by summary, separated by hyphens)

I wasn't quite sure where to list the supported fields, as I'm not sure on configuration field description limits. Happy to just pop the fields into the README for the extension.

Screencast

Customized branch name

Default branch name

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your first contribution! 🎉

🔔 @thomaslombart @FezVrasta @teziovsky @gavinroderick @michael-par @literallyjustroy @mheidinger @mikybars @luarmr @horumyy @rsperezn @Silv-1 @EyLuismi you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

Due to our current reduced availability, the initial review may take up to 10-15 business days 🎄

[pernielsentikaer]

Thanks for the enhancement @BehnH - can we do something like I did?

[BehnH]

Thanks for the enhancement @BehnH - can we do something like I did?

In the README & options, @pernielsentikaer? If so, I sure can!

[pernielsentikaer]

Hi 👋

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/raycast/jira

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.