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

jira #12528

Closed
pipedream-component-development opened this issue Jun 22, 2024 · 8 comments · Fixed by #12629
Closed

jira #12528

pipedream-component-development opened this issue Jun 22, 2024 · 8 comments · Fixed by #12629
Assignees
Labels
actions blocked Issue is blocked pending a resolution triaged For maintainers: This issue has been triaged by a Pipedream employee user request

Comments

@pipedream-component-development
Copy link
Collaborator

pipedream-component-development commented Jun 22, 2024

App

jira
https://community.atlassian.com/t5/Jira-Service-Management/HowTo-Update-Asset-Custom-Fields-via-REST-API/td-p/2514124

Actions

I would like to be able to update values stored within the project for custom fields, not custom fields inside a task.

Slack Discussion

https://pipedream-users.slack.com/archives/G01J50YGJGP/p1719408232566949

@Supermikeydee
Copy link

For a slightly better flow description--- if we go into Jira, goto issues, then edit custom fields from inside the project. We can add new values as options within the custom field "customers" where we are adding new customer names and Salesforce ID's. Appreciate any and all help as always---

@andrewjschuang andrewjschuang added this to To Do in Component (Source and Action) Backlog via automation Jun 26, 2024
@dylburger dylburger added the triaged For maintainers: This issue has been triaged by a Pipedream employee label Jun 26, 2024
@andrewjschuang andrewjschuang moved this from To Do to Prioritized in Component (Source and Action) Backlog Jun 26, 2024
@jcortes jcortes self-assigned this Jun 27, 2024
@jcortes jcortes moved this from Prioritized to Doing in Component (Source and Action) Backlog Jun 27, 2024
@jcortes
Copy link
Collaborator

jcortes commented Jun 28, 2024

Hi @malexanderlim I'm leaving this one as blocked because I started to get this error:

{"code":401,"message":"Unauthorized; scope does not match"}

where according to the documentation we need to add at least these two additional scopes

  • read:field.option:jira
  • write:field.option:jira

@jcortes jcortes added the blocked Issue is blocked pending a resolution label Jun 28, 2024
@malexanderlim malexanderlim moved this from Blocked to Prioritized in Component (Source and Action) Backlog Jul 17, 2024
@malexanderlim
Copy link
Collaborator

@jcortes we've added the two additional required scopes for this. Can you go through the auth flow again to pick up these new provisions and try again?

@jcortes
Copy link
Collaborator

jcortes commented Jul 17, 2024

Hi @malexanderlim I did test it again but unfortunately I'm still getting the same error

@jcortes jcortes moved this from Prioritized to Doing in Component (Source and Action) Backlog Jul 17, 2024
@jcortes
Copy link
Collaborator

jcortes commented Jul 18, 2024

@malexanderlim We can try to add these two additional scopes:

Read custom field contextual configurations.
read:custom-field-contextual-configuration:jira  

Save custom field contextual configurations.
write:custom-field-contextual-configuration:jira

@jcortes
Copy link
Collaborator

jcortes commented Jul 18, 2024

Ok I've just realized I was missing the las part of the path which is /option so now it's working! Thanks @malexanderlim

@jcortes jcortes moved this from Doing to Ready for PR review in Component (Source and Action) Backlog Jul 19, 2024
@GTFalcao GTFalcao moved this from Ready for PR review to In Review in Component (Source and Action) Backlog Jul 19, 2024
@GTFalcao GTFalcao moved this from In Review to Ready for QA in Component (Source and Action) Backlog Jul 19, 2024
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Jul 21, 2024
@vunguyenhung vunguyenhung moved this from In QA to Changes Required in Component (Source and Action) Backlog Jul 21, 2024
@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/jira-a43f052ac46e479fa9354bfca24dd97b

@jcortes jcortes moved this from Changes Required to Ready for QA in Component (Source and Action) Backlog Jul 22, 2024
@vunguyenhung vunguyenhung moved this from Ready for QA to In QA in Component (Source and Action) Backlog Jul 22, 2024
@vunguyenhung vunguyenhung moved this from In QA to Ready for release in Component (Source and Action) Backlog Jul 23, 2024
@vunguyenhung
Copy link
Collaborator

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/jira-a43f052ac46e479fa9354bfca24dd97b

Component (Source and Action) Backlog automation moved this from Ready for release to Done Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
actions blocked Issue is blocked pending a resolution triaged For maintainers: This issue has been triaged by a Pipedream employee user request
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

6 participants