[Jira] Optimize Issue Creation for Large Issue Creation Metadata#9330
[Jira] Optimize Issue Creation for Large Issue Creation Metadata#9330thomaslombart merged 10 commits intoraycast:mainfrom
Conversation
- Add the ability to start/stop watching issues - Initial commit
- Update minor versions of dependencies - Separate out the issue metadata per issuetype for optimization - Initial commit
|
Thank you for your contribution! 🎉 🔔 @thomaslombart @FezVrasta @igor9silva @jesperorb @teziovsky @gavinroderick @gavinroderick @michael-par you might want to have a look. |
- Update minor versions of dependencies - Linting - Update minor versions of dependencies
- Update minor versions of dependencies - Update minor versions of dependencies
thomaslombart
left a comment
There was a problem hiding this comment.
I forgot to ask you to update the CHANGELOG.md file in the watching issues PR. Could you rebase/merge your PR with the main branch, and add an entry in the changeling with the watching issues feature and your fix? Here's our guidelines about that: Version History.
|
There also seems to be a type error on the |
- Update minor versions of dependencies and fix added linting error - Update minor versions of dependencies
|
Published to the Raycast Store: |
|
🎉 🎉 🎉 We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag. |
Description
Previously when creating a Jira issue the panel would load all the data for all issue types for the specified project. For some organizations with excessive metadata, this response was too large and the process was running out of memory:
This changes the behavior so we will initially load the issue types for the specified project, then, we will load the issue type metadata per issue as it's selected.
Screencast
Checklist
npm run buildand tested this distribution build in Raycastassetsfolder are used by the extension itselfREADMEare placed outside of themetadatafolder