Olha Yevdokymova_SaaSJet Atlassian Partner

Thanks for the honest breakdown, @Bartosz Stankiewicz . The vote counts and the fact that JSDCLOUD-4922 has been open since 2017 say a lot about how common this need is. To answer your question from what we see: it’s often a mix. Staff approvers who’d rather stay in Jira, and external approvers (clients, vendors, finance…

Glad the collector bug was fixed. For anyone moving off issue collectors: a native JSM shareable link still asks external users to sign in or create a portal account, which is why you saw the login screen. If you need a form anyone can submit with no account at all, another approach you might consider is Smart Forms for…

Hi As Mikael and Marc explained, native forms can only make a field required through conditional sections. Once the field is linked to a Jira field, that means duplicating it in Jira. Another approach you might consider is Smart Forms for Jira (developed by my team). You can build the same idea without creating extra Jira…

Hi @André Christos explained the native limits well. An unchecked checkbox counts as empty, and “mandatory” on the JPD create form is all or nothing. Since you asked for other options, another approach you might consider is Smart Forms for Jira (developed by my team). It handles idea intake with its own form builder:…

Great overview, @George Ilie (AIGA Tech) The point about Rovo not reading native form answers (ROVO-317) is an important one, as more teams rely on AI search. Lets hope that for some users teamworkgraph will be helpfull but it is still not avaliable for everyone.As a part of Smart Forms for Jira we approach it a bit…

Hi @Colin Owen Ciro’s workaround with a status change plus an “Issue transitioned” rule is the cleanest native option on Data Center today. Another approach you might consider is Smart Forms for Jira (developed by my team), which is available for both Cloud and Data Center: Each form on a work item has its own shareable…

Hi @Mic Wang Sami’s design is the right one: put the mandatory selection before the approval status. The native portal Approve button ignores validators, so the order is what enforces it. If you’d like a simpler setup for the “form before approval” step, another approach you might consider is Smart Forms for Jira…

Hi @Md. Abrarul Huda Arek and Mertcan covered the native route: screen tabs in company-managed spaces. As Mertcan noted, a required field on a later tab is easy to miss, and in team-managed spaces tabs aren’t available at all. If the goal is to guide users through a long form so they don’t get lost, another approach you…

Hi @Karen Veltri John’s tip should help you find the Forms tab. Once you have it, keep in mind that native forms can be shared by link. Since embedding on your new intranet is the main goal, another approach you might consider is Smart Forms for Jira (developed by my team): Embed the form directly on your intranet (or on a…

Hi @Mary B_bw4pxu As Brant mentioned, native forms don’t support tabs or steps, so long forms end up as one long column. If you want a cleaner layout, another approach you might consider is Smart Forms for Jira (developed by my team): Multi-column layout: put fields side by side (for example First name and Last name, or…

Hi @Mayara Prado de Oliveira Arek’s checklist covers the native side well: the global public forms setting, the default reporter and IP allowlists are the usual blockers. If you keep running into permission issues, or need more control over the public form, another approach you might consider is Smart Forms for Jira…

Hi @Steve.Sigal Thanks for the detailed write-up. JPD-310 does sound like the cause, and Support is the right place for the bug itself. Your last point about the different Create buttons and data hygiene is something many teams run into. Another approach you might consider for Contributor intake is Smart Forms for Jira…

Hi @Jessica Alves, Moving from Excel and Word to direct submission into Jira is the step that removes the retyping. Brant’s suggestion to collect business cases through a form is the right direction. If some of your stakeholders don’t have Jira access, and adding JSM just for intake isn’t an option, another approach you…

Hello @Monique vdB Congratulations on great update! I have one problem with writting articles on the other groups against from App Central. Now my company have specific Solutions Department with some cases regarding Jira, Jsm and more that i would like to share(without any promotion) but I am not allowed to do it, the…

Hi @AGASTYA SHARMA A pattern we see a lot: a custom field gets created to capture one answer on a single request type, then never shows up in JQL, a dashboard, or automation again. Multiply that across teams and request types, and that’s where field sprawl comes from. A simple governance rule keeps it in check: Make it a…

Hi @Mike Roby As Trudy explained, in Software and Business spaces you can only drag existing Jira fields into a native form. You can’t create a form-only question there. If you need more flexibility, another approach you might consider is Smart Forms for Jira (developed by my team): Create form-only questions (text,…

Hi @Paulo.Cerqueira If the goal is for every new work item to come with a ready-to-fill structure, not just text in the Description, another approach you might consider is Smart Forms for Jira (developed by my team): Build a form that matches your table, with fields arranged in columns, so each row is easy to fill in.…

Hi @Chester Tan Arek and Mihai covered the root cause well. An anonymous submission still has to create a portal-only customer account on the fly, so both the global and space-level customer access settings have to line up. If your main goal is just to let people outside your site submit requests without logging in,…

Hi @Venkat Jira Admin As Shaik mentioned, transition screens aren’t shown on the portal, so a form plus automation is the realistic route. Another approach you might consider is Smart Forms for Jira (developed by my team). It works well for this kind of “fill this in before moving on” step: Create a short form with the…

Hi @Malee Great tips above: branching the form and creating sub-tasks from one rule both keep things maintainable. On the form side specifically, another approach you might consider is Smart Forms for Jira (developed by my team). It helps with the “unwieldy form that keeps changing” part: One form instead of many:…

Hi @Venkat Jira Admin Shaik’s native setup with conditional sections works well. As you saw, the tricky part is section dividers: every field after a conditional divider stays hidden until a new divider resets it. If your forms keep growing, another approach you might consider is Smart Forms for Jira (developed by my…

Hi @Wei Sheng Foo Until JRACLOUD-92229 and JRACLOUD-94138 are delivered, the “Default response” in the form builder and post-creation automation are the main native options. As you said, neither is ideal long term. Another approach you might consider is Smart Forms for Jira (developed by my team). It’s close to what your…

Hi @Aline Morimatsu The native CSAT link depends on a token that isn’t easy to get in automation, as Bálint mentioned, so the workaround article is the native route. Another approach you might consider is Smart Forms for Jira (developed by my team). With it you don’t need to build a token yourself: Create a short…

Hi @Mathew Lederman Christopher’s tip is a good one: the fewer clicks, the more responses. Native CSAT is hard to beat for a quick 1–5 score, but as you noticed, it gives you very little context. If you want richer feedback, another approach you might consider is Smart Forms for Jira (developed by my team). A setup many…

Hi @Jader Peixoto Volkmer Artyom’s advice is spot on: link to Jira fields only what you report on with JQL, and keep the line items inside the form. Another approach you might consider is Smart Forms for Jira (developed by my team). It makes this kind of order form easier to fill in and to report on: Responses are stored…

Hi @Tia Wagstaffe Marc and Gabriela are right about native Jira forms: it’s either licensed users only or a fully public form, and the JSM portal is the native workaround. If adding JSM just for this isn’t ideal, another approach you might consider is Smart Forms for Jira (developed by my team). It gives you more control…

Hi @Jye Barber As Divya mentioned, embedding CSM forms isn’t supported natively yet (CSM-26 is worth voting for). In the meantime, another approach you might consider is Smart Forms for Jira (developed by my team): Embed the form directly on your website, for example on your Contact us page, so visitors never leave it.…

Hi @Malay Nayak Ajay covered the native route well. Contributor forms work nicely for people with an Atlassian account. For people with no login at all, there’s no native public JPD form today. If you’re open to apps, another approach you might consider is Smart Forms for Jira (developed by my team). It covers exactly this…

Hi @ As James mentioned, native Forms can show or hide questions, but they can’t set a value and lock it while the user fills in the form. Another approach you might consider is Smart Forms for Jira (developed by my team). It gives you this behavior without automation fixing the value after submission: Create two versions…

Hi @Approving Authority James is right: the approval belongs in the workflow, not in a field the requester fills in. A “Waiting for Approval” status that holds the work item until the approver acts is the cleanest native setup. For the form side, another approach you might consider is Smart Forms for Jira (developed by my…