+3Conditional formatting is working well for us thus far on a JIRA card’s status (planning, execution, etc.). However, I am now trying to set conditional formatting on a card’s condition (On Track, At Risk, etc.).
For status, here is our formula and it works without issue.
Here is the same thing for condition and it is not working even though condition is a field the same exact as status.
Card details as seen here showing Status and Condition are both pulled in attributes.
Best answer by Leianne C
Hi $condition is unfortunately not one of the fields we normalize (since it isn't a universal property), so this.$condition doesn't exist in the formula system.
For Jira card data, we import all custom fields from the Jira instance, and some have picklist data types (status, for example, or potentially condition), and these have an underlying ID that represents the selected value as well as other properties like name. If condition is a picklist in your Jira instance, using this.condition.name might work instead.
For a list of available attributes, you can use the ATTRIBUTES function in a formula (e.g. adding =ATTRIBUTES onto a shape, for example), which will enumerate all available attributes.
Would you mind giving this a try and let us know if you see any improvements? Thank you!
+24Hi
Lucidspark’s Jira integration only surfaces certain fields on the card object that it syncs from Jira. Some fields, especially non‑standard or custom fields like Condition - may not be exposed to conditional formatting if they’re not mapped or supported by the integration.
Check the Data Panel on your Jira card in Lucidspark to confirm that the Condition field is actually present and has the values you expect. If it isn’t available there, the conditional rule won’t ever trigger because the card has nothing for it to evaluate.
To learn more - Supported custom fields for Jira integrations in Lucidspark | Community
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
+3Huma,
Condition is mapped and fully supported as it shows on every card.
Small snippet from a card listed on JIRA board. “On Track” is condition field.
In the Card details, it is listed:
+24Hi
Thanks for the insight, seems the syncing is all fine and some things needs to be checked on the field structure, maybe we can wait / take it to the Lucid internal team to take a closer look.
Best Regards
+15Hi $condition is unfortunately not one of the fields we normalize (since it isn't a universal property), so this.$condition doesn't exist in the formula system.
For Jira card data, we import all custom fields from the Jira instance, and some have picklist data types (status, for example, or potentially condition), and these have an underlying ID that represents the selected value as well as other properties like name. If condition is a picklist in your Jira instance, using this.condition.name might work instead.
For a list of available attributes, you can use the ATTRIBUTES function in a formula (e.g. adding =ATTRIBUTES onto a shape, for example), which will enumerate all available attributes.
Would you mind giving this a try and let us know if you see any improvements? Thank you!
+3
It looks like condition is not a known attribute, unfortunately. Trying ‘this.condition.name’ also did not work.
+15Hi
Please let us know if you have any questions in the meantime!
+15Hi this.$condition which unfortunately will not exist; it's important to only include the $ when using attributes. Attributes are accessible as =ATTRIBUTES or =ATTRIBUTES(this) for a current shape (it enumerates the attributes on the shape). Our engineers advised that because of this, what you have in the screenshot will not work.
If this.condition.name doesn't work, can you please try using this.condition. This might returning the ID which you can use for conditional formatting.
Please let me know if you experience any issues with this, or if you have any questions!
+15Hi
Thanks for your help! Please let us know if you have any questions in the meantime.
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
A Lucid or airfocus account is required to interact with the Community, and your participation is subject to the Supplemental Lucid Community Terms. You may not participate in the Community if you are under 18. You will be redirected to the Lucid or airfocus app to log in.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
