The #viewissuesidebar selector presently used by the extension to identify the container into which the button gets injected is no longer available in the markup for the issue detail page rendered by the new Jira issue view.
Browsing the DOM of the pages rendered by the new view, the markup uses few IDs and the class names rendered for the vast majority of the divs use machine-generated names that are not reliable to target elements, which breaks the extension's abilities to both place the a.) "Send to OmniFocus" button and b.) scrape the issue's summary, description, etc.
⚠️ I'm presently working on a from-scratch rewrite of this extension, which will only support Jira's "new" ticket view. And, since Atlassian has clearly expressed that this updated markup is clearly the future of Jira, it doesn't seem to me like fixing the problem for this extension is a valuable investment of time.
That said, I'm entirely happy to review a good ol' fashioned pull request 🙏🏼
The
#viewissuesidebarselector presently used by the extension to identify the container into which the button gets injected is no longer available in the markup for the issue detail page rendered by the new Jira issue view.At the time of this writing, Atlassian allows you to toggle the new view.
Browsing the DOM of the pages rendered by the new view, the markup uses few IDs and the class names rendered for the vast majority of the divs use machine-generated names that are not reliable to target elements, which breaks the extension's abilities to both place the a.) "Send to OmniFocus" button and b.) scrape the issue's summary, description, etc.
⚠️ I'm presently working on a from-scratch rewrite of this extension, which will only support Jira's "new" ticket view. And, since Atlassian has clearly expressed that this updated markup is clearly the future of Jira, it doesn't seem to me like fixing the problem for this extension is a valuable investment of time.
That said, I'm entirely happy to review a good ol' fashioned pull request 🙏🏼