Jira Issue Creator in Chrome - Screen&Draw

Contrary to the message below, I don't have any performance problem but I totally agree with the Goal #2.1, this is critical for us for widespread usage in our company. I see a very easy (front-end wise) way to do that: Use the "Identify duplicate task" that already exist. Once detected, select the entry and it will add a comment instead of creating a new issue. Nothing more is needed but even better, use the Jira task ID in the comparison so it can detect even quicker a "duplicate" task.

UPDATE: SaaSJet's team got back to me and the below is on the roadmap for 2025! Hoping they win it all! 👏 Hi Team, First, let me just say that I’ve been a SaaSJet fan for a long time. 🙂 Not only does the team respond exceptionally quick and build to fill in the UX and functionality gaps left behind by Atlassian, their team is from Ukraine, so are some of the most hardworking and badass folks on the planet, and I hope they absolutely crush it with this new and much-needed product. #StandWithUkraine 🇺🇦 Now, while I absolutely love the idea of increased functionality that SaasJet’s "Jira Issue Creator in Chrome - Screen&Draw" Chrome Extension aims to provide over Atlassian’s "Jira Product Discovery" Chrome Extension... I’ve been struggling with SaaSJet’s Jira Issue Creator because: 1) PERFORMANCE ISSUE: First and foremost, it takes on average 12 seconds to open or refresh/activate (where I just see the spinning progress bar) every single time I click the extension or click “Settings” and go back. This consistent delay causes the extension to be just as [in]efficient as opening up Jira and creating a new Issue with shortcut “C.” I already tried disabling “Show Page Editor,” but that only saved ~1.5 seconds. **How can I fix this?** 🙏 2) MISSING KEY FEATURES: While I’ve left Atlassian important feedback about their own extension (see below), their extension does add two critical things I wish could be added to SaaSJet’s Chrome Extension, albeit with some changes I’ve detailed below: — (i) you can add to an existing Jira Issue and — (ii) you can easily include the URL and add already-selected text on the webpage extremely efficiently. However, as Atlassian typically does, they miss out on critical components of the UX that I hope SaaSJet immediately uses to capitalize and dominate this market. SaaSJet would benefit from at least 10,000 installs (read: users) if it goes further than what Atlassian did since Atlassian left the door wide-open for someone to come in and innovate beyond them—and SaaSJet appears to be best poised to do this if it acts fast. **Thus, how can we achieve Goals #1 and #2 with SaaSJet’s Chrome Extension here?** (Hoping it's figured out soon so I can bring this to all my companies!) 🙏 --- --- ---- Jun 25, 2024 [...] It'd be a blessing to be able to do #1 and #2 below (via this Chrome Extension) when on a web page: GOAL #1) Create a "Draft" Issue in any Project (e.g. in all our Workflows, we have a ~"Draft" status before ~"Ready") with: — a) screenshot(s) of the current web page ➡️ into the Description and/or as Attachment(s) — b) its URL ➡️ into the Description (like the official Slack-Jira integration) — c) any selected text or elements on the page ➡️ into the Description — d) some additional context we can provide and type ➡️ into the Description or as a Jira comment GOAL #2) Comment on any existing Issue with: — a) screenshot(s) of the current web page — b) its URL — c) any selected text or elements on the page — d) some additional context we can provide and type 4 out of 4 found this helpful

People using enterprise versions cannot use it ?