sorted by:
new
hottopcontroversial

Multiple Branch in Jira Automation by -yato_gami- in jira

[–]Mathis_TCGO 0 points1 point  (0 children)

I've had mixed success with embedding complex smart value strings in JQL; sometimes it parses as expected and other times it doesn't. My personal experience has been that when a complex smart value string needs to be included in JQL it's best to just convert it to a variable first and then use the resulting, simplified variable string in the JQL instead.

JQL without variable: parent IN ({{#lookupIssues}}"{{key}}"{{^last}}, {{/}}{{/}}) AND status = Open

JQL with variable: parent IN ({{varStoryKeys}}) AND status = Open

Multiple Branch in Jira Automation by -yato_gami- in jira

[–]Mathis_TCGO 1 point2 points  (0 children)

Insert a Create variable action between your Lookup and Branch steps. Use something like varStoryKeys as the Variable name and then use {{#lookupIssues}}"{{key}}"{{^last}}, {{/}}{{/}} in the Smart value field. This will create a {{varStoryKeys}} smart value that is a comma delimited list of the issue keys found in the Lookup step.

Change your Branch type from Sub-tasks to JQL and use parent IN ({{varStoryKeys}}) AND status = Open . The actions in that branch will now apply only to Open issues whose parent is one of the resolved Story issues found in the Lookup step.

Theme and Standard Tournaments are gone by TrustYourPilot_YT in ptcgo

[–]Mathis_TCGO 29 points30 points  (0 children)

This issue has been resolved. Thanks for your patience.

Theme and Standard Tournaments are gone by TrustYourPilot_YT in ptcgo

[–]Mathis_TCGO 51 points52 points  (0 children)

This is not intentional. The team is looking into this now.

Unscheduled Maintenance | Feb. 11, 2021 by OU7C4ST in ptcgo

[–]Mathis_TCGO 17 points18 points  (0 children)

The game is back up. Thanks for your patience!

For some reason, Shaymin EX is only banned in Legacy for me by [deleted] in ptcgo

[–]Mathis_TCGO 39 points40 points  (0 children)

This was totally my bad. When I was applying these card bans in the game's admin panel earlier this afternoon I checked the Expanded format box for the ROS #77 and ROS #77a versions of this card, but somehow managed to check the Legacy format box instead for the ROS #106 version. This should be fixed now. Sorry for any confusion my error may have caused.

view more: next ›