Connector Improvement: Jira Connector Table Blocking
PlannedIt would be great if the Jira connector could support Table blocking.
This would allow us to control the amount of MAR we consume for Jira whilst we incrementally explore the business value that different tables in Jira provide.
For example, the "Issue Field History" table makes up the vast proportion of Jira MAR whilst initial exploration and value might only initially start with Project and User tables etc.
-
Official comment
Hi Alastair, thanks for this request! (And thank you Anthony for the validation.) This definitely seems like a useful feature– I will add it to our backlog.
-
agreed, the inability to control which jira tables are synced makes this connector useless to my organization.
-
agreed aswell, we have disabled ours until this is available.
-
Is there any update on this?
Issue Field History is still causing a lot of MARs unneccessarily, which really burn a hole in current pricing scheme -
My organization has no need for "Issue Field History" or "Issue Multiselect History" yet together they make up 95% of the MAR for this connector. And the total MAR makes it the second-highest MAR connector we have. Why do we have to pay so much for tables that we don't use?
Please sign in to leave a comment.
Comments
5 comments