-
Bug
-
Resolution: Timed out
-
Low
-
Severity 3 - Minor
-
When sorting inline tasks inside a Connect add-on using the task report macro, an error is thrown (see screenshot).
- relates to
-
CONFSERVER-41551 Cannot render macros from content rest API
-
- Closed
-
[CONFCLOUD-52776] Sorting inline tasks does not work in Connect macros
Resolution | New: Timed out [ 10 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | Original: affects-cloud cc-platform content-rendering | New: affects-cloud cc-platform content-rendering stale-bulk-close |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2364077 ] | New: JAC Bug Workflow v3 [ 3419837 ] |
Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Labels | Original: affects-cloud content-rendering | New: affects-cloud cc-platform content-rendering |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2239621 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2364077 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2200756 ] | New: Confluence Workflow - Public Facing - Restricted v5 [ 2239621 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2135241 ] | New: Confluence Workflow - Public Facing - Restricted v5.1 - TEMP [ 2200756 ] |
Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 1892046 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2135241 ] |
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!