You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 text was updated successfully, but these errors were encountered:
prometheas
changed the title
Extension fails to work with CSS selector changes on Atlassian-hosted Jira service
Extension fails to work with the "new Jira issue view" (button doesn't appear, etc)
Aug 10, 2020
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.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.
That said, I'm entirely happy to review a good ol' fashioned pull request 🙏🏼
The text was updated successfully, but these errors were encountered: