True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)
Here is the screenshot from my integration

True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)
arvind.choudhary: Can one Jira work item type be both a requirement type and a defect type in the integration? Currently , the integration is not possible , so it has to be done as i wrote in my previous step
True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)
Based on the issues reported in this thread, these two questions may help narrow down the cause: Can one Jira work item type be both a requirement type and a defect type in the integration? Does the 400 on issuetypes/metadata mean no defect type was stored, or could it have another cause?
True Platform issues
thanks bro , but my actual birth date is 1st May , this one is the paper one. you know how it works

True Platform issues
Happy Birthday @Monty_Bagati . Many more returns of the day.
True Platform issues
Monty_Bagati: Tests created through True AI cannot be scheduled and needs to be executed manually Totally agreed
True Platform issues
Monty_Bagati: The executions runs are also not reliable and they get stuck most of the times without any reason. And the worst part is that if the execution gets stuck then the True platform does generate any error log for us to investigate about what was the root cause .
True Platform issues
Monty_Bagati: It fails to reason and self heal the steps (Requirement description ) that are described in the requirement and fails badly while executing the test steps This point is also valid
True Platform issues
Monty_Bagati: True platform execution is extremely slow , it almost takes 4x more time than it would take using any other open library tool For this point also I will agree. It takes more than compared to other tools
True Platform issues
Monty_Bagati: True Paltform is unable to reason on a simple thing while automating a basic website like Cura health. It is not able to automate any website unless you spoonfeed and hand held every aspect even the minor things in the requirement Yes, I completely agree. Another challenge is that the AI-powered “Analyze” button is not very accurate at the moment. Most of the time (around 95-96%), it labels the issue as an automation bug, even when the real cause lies something else. I created a…
True Platform issues
Some critical issues in True Platform True Paltform is unable to reason on a simple thing while automating a basic website like Cura health. It is not able to automate any website unless you spoonfeed and hand held every aspect even the minor things in the requirement True platform execution is extremely slow , it almost takes 4x more time than it would take using any other open library tool It fails to reason and self heal the steps (Requirement description ) that are described in the…
True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)
There is one more integration issue that has come up recently. If i want to sync all work items as requirements and select everything as below , i wont be able to integrate JIRA with true I have to either uncheck the Bug Mapping from Step 2 or uncheck some of the issue types from requirement fielsa nd value mapping and then check it in defect fields and value mapping

True AI Tester Certification Progress Stuck at 90%
yes. certificate frequency needs improvement
True Platform: “Report Defect > Create new defect” fails with Jira (400 on issue type metadata; “Issue type is not configured for defects”)
Environment: Katalon True Platform (beta), instance true-platform-beta-4.katalon.io, project AutoGen (ID 3567815). Jira Cloud integration, project Team Fire (key FB), connection ID 103674, integration ID 127823. Problem: In Executions > History > a failed test run > Tests tab > Report Defect > Create New Defect, the Issue Type shows “Bug” but the form never displays any fields. The text “Select an issue to display fields here” stays on screen, and the Create button stays disabled. I can still…
How to perform two finger drag to pan using katalon studio
Check how your app reads the gesture. In some apps (maps, for example) a two-finger vertical drag means tilt, not pan, so test it manually first, then verify the result in the script (compare an element’s location or a screenshot before and after).
How to perform two finger drag to pan using katalon studio
Both fingers need the same number of actions and the same durations, or they won’t move together. Make the move slower (e.g. 800 ms or more) for a controlled pan, since a fast move can be read as a fling.
How to perform two finger drag to pan using katalon studio
Avoid hard-coded pixels, which only fit one device. Read the screen size from driver.manage().window().getSize() (or the target element’s bounds) and calculate start and end points as percentages.
How to perform two finger drag to pan using katalon studio
A few things to watch: PointerInput/Sequence are Selenium 4 classes. If you get a “class not found” error, your Studio version probably bundles an older client, so check which Selenium/Appium client your version ships.
Authen in web when use Desktop testing
If the app gets the token back via a custom-protocol link, the browser may show an “open app?” prompt that also needs handling.
Authen in web when use Desktop testing
If debuggerAddress has no effect as a plain capability, try it inside goog:chromeOptions
Authen in web when use Desktop testing
As far as I know, Chrome forwards a new link to the running instance using the same user-data-dir. A link fired by the OS default-browser handler normally goes to the default profile, while the debug instance runs from C:\katalon\chrome-profile, so the login URL may open in a different Chrome than the one Katalon is attached to. Recent Chrome versions also ignore --remote-debugging-port on the default profile, so you can’t just use that. Worth confirming which window the link actually opens in.…
True AI Tester Certification Progress Stuck at 90%
Usually, it takes a few days for the information to get updated. Since this delay happens quite often, it would be great if the team could improve the update frequency.
[True Platform] Why isn't the acceptance criteria syncing with True Platform?
is this scheduled for an upcoming release?
[True Platform] Why isn't the acceptance criteria syncing with True Platform?
Many teams keep most requirements in that field and can’t move them into Description (org policy, as @akshay_sartabe said), so a configurable field mapping in the integration settings would be the ideal fix.
Unable to Inspect Jetpack Compose testTag Elements in Katalon Mobile Spy
To separate app-side issues from Katalon-side ones, dump the screen directly: adb shell uiautomator dump /sdcard/window.xml, pull the file and search for your tag in resource-id. If it’s there, Mobile Spy will see it too.
Unable to Inspect Jetpack Compose testTag Elements in Katalon Mobile Spy
If a tag sits on a child inside a clickable or merged parent (e.g. a Text inside a Button), the merged node may only expose the parent’s tag. Put the tag on the parent, or avoid merging for that element.
Unable to Inspect Jetpack Compose testTag Elements in Katalon Mobile Spy
As far as I know, dialogs, bottom sheets and popups are separate windows, so the flag on the screen root doesn’t reach them. Set it inside their content too.
Unable to Inspect Jetpack Compose testTag Elements in Katalon Mobile Spy
I will add couple of points First make sure the change is actually in the build you’re spying on. testTagsAsResourceId is only available in newer Compose versions, so if your dev can’t use it, upgrade Compose first. After adding the flag, ship a new build, reinstall the app and refresh the page source in Mobile Spy.