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

[BUG] Jira update issue - cannot use custom expression for issue id or key #8494

Closed
willman14 opened this issue Oct 16, 2023 · 3 comments · Fixed by #8550
Closed

[BUG] Jira update issue - cannot use custom expression for issue id or key #8494

willman14 opened this issue Oct 16, 2023 · 3 comments · Fixed by #8550
Assignees
Labels
bug Something isn't working triaged For maintainers: This issue has been triaged by a Pipedream employee

Comments

@willman14
Copy link

Describe the bug
Using a custom expression for issue id or key, returns Error - Request failed with status code 400

To Reproduce
Steps to reproduce the behavior:

  1. Add update issue jira component
  2. Add account
  3. Add cloud id
  4. Put in a custom expression for Issue id or key
  5. Fields should refresh after but you get Error - Request failed with status code 400 below the refresh fields button

Expected behavior
When you click refresh fields, the fields should load.

Screenshots
Screenshot 2023-10-16 at 15 36 58

Desktop (please complete the following information):

  • OS: macOS 12.5
  • Browser: Chrome 118
  • Jira Update component version: 0.2.7

Additional context
If the issue key or id is put in manually, the fields load.

@willman14 willman14 added the bug Something isn't working label Oct 16, 2023
@vunguyenhung
Copy link
Collaborator

Hi, I can reproduce your issue
image

For dev: I would suggest to allow user to select the Issue Type to get additional props, instead of depending on the issue id, since they might be dynamic

@vunguyenhung vunguyenhung added this to To Do in Component (Source and Action) Backlog via automation Oct 16, 2023
@dylburger dylburger added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Oct 16, 2023
@malexanderlim malexanderlim moved this from To Do to Prioritized in Component (Source and Action) Backlog Oct 19, 2023
@michelle0927 michelle0927 self-assigned this Oct 20, 2023
@michelle0927 michelle0927 moved this from Prioritized to Doing in Component (Source and Action) Backlog Oct 20, 2023
@michelle0927 michelle0927 linked a pull request Oct 20, 2023 that will close this issue
@michelle0927 michelle0927 moved this from Doing to Ready for PR review in Component (Source and Action) Backlog Oct 20, 2023
@vellames vellames moved this from Ready for PR review to Ready for QA in Component (Source and Action) Backlog Oct 23, 2023
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Oct 24, 2023
@vunguyenhung vunguyenhung moved this from In QA to Changes Required in Component (Source and Action) Backlog Oct 24, 2023
@vunguyenhung
Copy link
Collaborator

Hello everyone, I have tested this PR and there're some test cases failed or needed improvement.

Please check the test report below for more information
https://vunguyenhung.notion.site/BUG-Jira-update-issue-cannot-use-custom-expression-for-issue-id-or-key-bef0e86876fa4e7fb6a46a8da30469f4

@michelle0927 michelle0927 moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog Oct 24, 2023
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Oct 25, 2023
@vunguyenhung vunguyenhung moved this from In QA to Ready for release in Component (Source and Action) Backlog Oct 25, 2023
@vunguyenhung
Copy link
Collaborator

Component (Source and Action) Backlog automation moved this from Ready for release to Done Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triaged For maintainers: This issue has been triaged by a Pipedream employee
Development

Successfully merging a pull request may close this issue.

4 participants