You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
While the UX in the "New Issue View" is generally a win in every way I can think of, as the author and maintainer of the Jira to OmniFocus extension, I must report that the lack of semantic class names and/or element IDs in the markup makes it very difficult to reliably place that "Send to OmniFocus" button cleanly into the UI.
Inspecting the DOM, the markup generated by this new view uses a bunch of machine-generated class names, like `div.sc-imYgaF.cEhqTj`, `div.sc-eAKXzc.idCLPT.sc-BngTV.jLfydQ`, and `div.sc-cqpYsc.dpswfB.sc-bFADNz.eeRmMw` 😬
At the moment, the only thing I can think to do is to display a notification to my users that the extension is incompatible with the new view, and that they can revert to the old issues view, but that's kind of gross for everyone.
Anyway, if it's possible to add some semantic classes (or even some more of those `data-test-id` attributes) to the rendered DOM, I'd be most grateful 🙂🙏🏼