Olha Yevdokymova_SaaSJet Atlassian Partner

Hi @Akash Right now, the built-in form builder only provides input fields (short text, dropdowns, paragraph, etc.), so there isn’t a true “static content” or “header” element to visually separate sections. That’s why using a text field as a workaround feels messy — Jira still treats it like user input rather than…

Hi @Ariel Ramos Thanks and good luck😉

Hi @Manish Taneja Great question — you’re right that Jira Service Management’s request forms don’t yet work quite like Freshdesk when it comes to true conditional field visibility. 🔹 What You Can Do Natively in JSM JSM now includes section logic on portal forms (rolled out in 2024): You can create form sections and apply…

 Hi @Ariel Ramos By default, the “Send email” action in Jira Automation is pretty limited (plain text or very simple formatting). If your first project is sending a polished HTML email, it’s likely powered by a legacy Zapier setup, Apps Script, or an old integration someone built before. Quick Fix: Improve Your Jira…

Hi @Humberto Gomes! 👋 You're absolutely right — Jira Cloud dashboards don't natively support direct Asset (formerly Insight) views. Unfortunately, there are no out-of-the-box gadgets that pull data straight from Assets unless those assets are linked to issues. 🛠️ What Can Work: If Assets are connected to issues via custom…

Hi @JoAnn Pruden Great question — this is a common challenge when working with dashboards and linked issues in Jira. Unfortunately, JQL (Jira Query Language) doesn't currently support filtering based on the status of linked issues out of the box. That’s why your dashboard includes items where the linked tickets are already…

Hi, @HQRAZAHS 👋 I totally get the frustration — Jira's Summary page isn't always customizable the way we want. If you’re looking for a solution that shows board-specific summaries, one approach you might want to try the Forge Apps Generator developed by my team. It lets you build custom Jira apps and dashboards using…

Hi @Cecilia Rodriguez In native JSM, forms and their responses don’t persist when you clone an issue — cloning only copies Jira field values, not the embedded form. There’s also no export/import option to move a form submission to another issue. That’s why your cloned Jira Software tickets lose the original structured…

Hi @Frank Petri You’ve spotted one of the current limitations of native JSM/Jira Forms — there’s no built-in way to pre-fill a field value (especially hidden from the user) on a public form. Every field shown in the form needs to be completed by the submitter, and if you want a constant value like Product Manager = John…

Hi @Katie Lee In native JSM, portal forms can only be used by people who have the right project access — usually agents, collaborators, or customers already added to the service project. If your stakeholders aren’t set up as customers in that project, they won’t be able to open the link or submit it. That’s why they’re…

Hi @Jeffrey Bistrong If you ever decide to try an app to solve this:With Smart Forms for Jira (developed by my team), you could: Create a form with all the fields you want. Map the all responses directly into the description field or any other field or even dont map at all instead of custom fields. Share the form…

Hi @Bradley Appelgate In native Jira/JSM, forms are scoped to a single project — there’s no built-in way to make one “global” template that you can just drop into any other project. That’s why you’re not seeing your form in other projects after creating it. If you want true reusability across all projects, a practical…

Since in Jira Cloud the Behaviours module does not provide setError() function and you are trying to guide users (not only block them), another approach you might consider is using Smart Forms for Jira (my team’s app) for the input step and then mapping the answers back to Jira: Put guidance right next to questions with…

Hi @Nikhil Ninan In JSM, you can use conditional logic to show or hide sections or fields based on a selection — so you could set your “Parent” dropdown (Head, Arm, Leg) to reveal a section with related fields. That works if you just need a few fields grouped under each option. You could build similar form it in Smart…

Hi @Sebastian Krzewiński In native Jira, dynamic show/hide for fields is available in JSM portal forms (like you mentioned), but the standard Create Issue screen doesn’t support conditional logic out of the box. Field visibility there is static — you’d need custom scripts or apps to make it behave dynamically. A practical…

Hi @Darius Fields You’re right — native JSM request type forms don’t currently allow you to display a static image inline. The built-in fields cover attachments, but those are for upload, not display. If you want to add an image to guide requesters (for example, a diagram, chart, or product options photo), one option is…

Hi @Alejandra Martin If your are open to use apps, you may want to check Smart Forms for Jira developed by my team. External Sharing is an Intended Feature — But Controlled by Settings Smart Forms allows you to share forms via public URLs, even with users outside Jira. This is by design, especially for use cases like:…

Hi @Jeffrey Bistrong, If you're looking to collect structured, required data across multiple projects with minimal overhead, you might want to check out app developed by my team Smart Forms for Jira. Here’s why it could be a great fit for your setup: Supports Required Fields – You can enforce mandatory fields at the form…

Hi @Tom langton Yes, conditional logic works great! Assets fields aren't supported yet, but we're actively working on it since it's been highly requested. Should be ready this quarter if everything goes well.🙂 For now you can test it. We recently added to Smart Forms Capcha for external protection of form submissions and…

Hi @Yvonne Sutter Thanks for all the DC requests - Smart Forms is finally there! Form builder, conditional logic and most features are live now. External sharing isn't available yet (same as Confluence), but we're targeting a release this month. Worth testing the core functionality to see if it works for your setup. Before…

Hello @britney.zhou It sounds like you're doing some heavy lifting with JSM + connectors + automation to bridge those gaps. 😅 If you're open to simplifying things, here's an alternative approach with app developed by my team: Use Smart Forms for Jira to Intake Ideas Directly into JPD Smart Forms allows you to create…

Hello @Perry Forster You may want to try add-on Smart Forms for Jira developed by my team that supports reporter field and allows you to set this one as mandatory. 1. Add a Selection Field to Your Form Create a dropdown field in your Smart Form labeled “Select Reporter” Use pre-fill form options to pull in a list of users…

Hi @Jesse Zamazanuk , It sounds like you're running a well-structured prioritization workflow—and you're right, Jira Product Discovery (JPD) doesn't yet have native support for stack-ranked prioritization by stakeholder group in the same drag-and-drop way as Aha!. Here's how Smart Forms for Jira can help bridge the gap and…

Hi @Liam Maloney , Great use case! The key to making this work smoothly is leveraging form field mapping to Jira issue fields, which then enables reliable automation rules. The Challenge with Direct Form Automation: Jira Automation has limited direct access to form submission data, which is why you're struggling to get…

Hi @Rosa M Fossi You're experiencing the limitations of Jira Software's built-in forms, which are indeed quite basic in terms of styling and professional presentation. It lacks conditional logic and other options to make forms more usable. For JSM Projects: If you can move your use case to a Jira Service Management…

Hello @Jay McKelvey Unfrotunatly, Jira Cloud native forms doesn't support any sections or conditional logic. If you are okay with add-ons you can try Smart Forms for Jira developed by my team - this ones supports conditional logic to show or hide multiple questions based on preuvios choices, plus there are content…

Hi @Sheila Connolly The tutorial you found was likely for Jira Service Management (JSM) forms, which have built-in conditional logic. However, in Jira Software projects, the native forms don't include this conditional functionality. For conditional logic in Jira Software projects, you'll need to use an add-on like Smart…

Hi @Jay McKelvey You're absolutely right about that limitation with native Jira Forms - they do require mapping each question to a specific Jira field, which can be restrictive when you want to collect data that doesn't necessarily need to become permanent issue fields. If you need more flexibility in how form data is…

Hi @PLaksh11 ! If you're open to alternatives beyond ScriptRunner, one way to simplify this (and avoid complex behaviors scripts entirely) is by using Smart Forms for Jira – an app developed by my team. It’s available for Jira Cloud and lets you: ✅ Use multi-select fields with conditional logic, so you can show or hide…

Hello @Clare Lawson I saw you reached out to our Support Team earlier — just checking in to see if everything is working fine now? Let me know if you still need help!