Could not find valid 'id' or 'value' in the Parent Option object (Beta update for custom fields)

[EkaterinaVlasova]

Steps to reproduce

** Provide a set of unambiguous steps to reproduce this bug include code, if relevant **

1. Select to pull bug tickets from the selected filter with added custom fields (all data was imported successfully)
2. Make an update to a value of 2 custom fields (i have project_team and feature as custom fields, both one value without commas)
3. Select column titles and the values
4. Select to Update Jira tickets

Expected result

1. Values that were previously empty in the custom fields, should get the expected new values

Actual result

1. [Screenshot, logs] Could not find valid 'id' or 'value' in the Parent Option object.

Notes: i have used Jira map function to see the IDs of those custom fields, and have tried to change the Column titles with those IDs instead, but still same error..

[ljay79]

Thx for reporting. I will have a look into that asap

[EkaterinaVlasova]

please let me know if i could provide any more details about this, i found the debug mode but the error message doesn't show anything extra when debug is enabled...

[ljay79]

Hi, so.. the addon is back online, to further investigate i like to ask you to follow these steps:

• go into "About" dialog
• enable debugging
• take note of the "temp. user key" and report it here.
• perform the actions which causing the errors
• report back here with a rough time frame you did the steps above

[EkaterinaVlasova]

Hello, ALEt7zRrAaUo241FqASdHCL6bXR31dRnebuiKus+roH/svlm2Q2W8bv94NhFPRYisQBj0Tz/JjFQ 15 july, uk time: 21:27

however now i think i got a different error: Funktion forEach in Objekt Mobile SDK, Navigation nicht gefunden

[EkaterinaVlasova]

at 21:30 i have unchecked Summary, Components, Description fileds, cause i have only updated Feature and Project_team and now i got my original error message:

Project_Team: Could not find valid 'id' or 'value' in the Parent Option object., Feature: Could not find valid 'id' or 'value' in the Parent Option object.,

[ljay79]

Thx for the feedback. I will have a look soon. Please keep in mind that this part is a Beta feature and development on that part had became stalled...

[EkaterinaVlasova]

thanks a lot for the fast reply. i think this is a very cool feature, i managed to see it working for another jira project where i had no errors, and also updated a custom field. if only your tool could also import test cases from testrail and upload back to testrail ... :)

[paul-lemon]

Hi @ljay79 - I can try find some time to look at this if you like. I think the issue is related to the same problem here https://community.atlassian.com/t5/Jira-questions/Error-creating-issue-via-REST-API-could-not-find-valid-id/qaq-p/370628 @ljay79 can you send me the debug info? @EkaterinaVlasova - the issue is likely caused by using the names of the Feature and Project_Team where Jira's API by default wants the internal ID of these elements. It may be possible to set them by name.

[ljay79]

Any update on this topic @paul-lemon ? :)

[paul-lemon]

@ljay79 - happy to look but I need the debug info from the logs.

[ljay79]

Sry @paul-lemon apparently i was waiting to long to catch up on this topic. There is no such logs anymore. Stackdriver does not keep them forever.

If you guys wanna re-evaluate that topic and produce new logs, give me a ping and i fetch them more faster this time.

[paul-lemon]

Hi @EkaterinaVlasova - if you would like me to look at this problem can you reproduce the problem while following these steps so I can see the log files from JIRA

• go into "About" dialog
• enable debugging
• take note of the "temp. user key" and report it here.
• perform the actions which causing the errors
• report back here with a rough time frame you did the steps above