Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add child issues to Jira extension #15204

Open
wants to merge 16 commits into
base: main
Choose a base branch
from
Open

Conversation

horumyy
Copy link

@horumyy horumyy commented Nov 2, 2024

Description

Implemented the functionality to display child issues in the IssueDetail.tsx component. Additionally, a new option named “Open Child Issues” has been added to the action panel, enabling users to navigate through the child issues.

Screencast

Screenshot 2024-11-03 at 2 14 56 p m
Screenshot 2024-11-03 at 2 15 13 p m

jira.mp4

Checklist

- added Child Issues
- Initial commit
@raycastbot raycastbot added extension fix / improvement Label for PRs with extension's fix improvements extension: jira Issues related to the jira extension labels Nov 2, 2024
@raycastbot
Copy link
Collaborator

raycastbot commented Nov 2, 2024

Thank you for your first contribution! 🎉

🔔 @thomaslombart @FezVrasta @teziovsky @gavinroderick @michael-par @literallyjustroy @mheidinger @mikybars @luarmr 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.

You can expect an initial review within five business days.

- added Child Issues
- removed contributor
- fixed errors related to fetching
- added Child Issues
@horumyy horumyy changed the title Update jira extension added action button once inside issueDetail Nov 2, 2024
@horumyy horumyy changed the title added action button once inside issueDetail Add child issues to Jira extension Nov 2, 2024
pernielsentikaer and others added 3 commits November 6, 2024 21:55
wrong github name was provided
i guess name it supposed to be the one on the raycast account
@horumyy
Copy link
Author

horumyy commented Nov 13, 2024

Is there anything else that needs to be checked in this pr? or anything that needs to be corrected for merge? @thomaslombart

@thomaslombart
Copy link
Collaborator

Yes, I left a comment just above.

@horumyy
Copy link
Author

horumyy commented Nov 14, 2024

Yes, I left a comment just above.

sure? i dont see it

);

const isEpic = issue.fields.issuetype?.name === "Epic";
const { issues: epicIssues, isLoading: isLoadingEpicIssues } = useEpicIssues(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why having two useEpicIssues in the component? Can't they be combined into one?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch, fixed on latest commit! :)

@thomaslombart
Copy link
Collaborator

Oh indeed, it was a pending comment, sorry! 😅

- Merge branch \'contributions/merge-1731595802691143000\'
- Pull contributions
- removed duplicated hook call
@horumyy
Copy link
Author

horumyy commented Nov 14, 2024

Thank you for your comment c:, fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extension fix / improvement Label for PRs with extension's fix improvements extension: jira Issues related to the jira extension
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants