Olha Yevdokymova_SaaSJet Atlassian Partner

Hi @Shandy Tailor Jira’s Forms panel isn’t designed for rich copy/paste. Atlassian doesn’t document a guarantee that text copied directly from the embedded form will preserve/transfer cleanly. Instead, Atlassian points admins to view/download form responses and/or work with the values via Automation or export. If your…

Hi @PATRICIA MURPHY Right now, Jira Cloud doesn’t have a built-in setting to require users to create issues through a specific form. Forms in company-managed projects can be attached to an issue type (like Bug), but users can still use the standard “Create work item” button or quick-create option — Jira doesn’t yet provide…

Hi @Vikrant Yadav That’s a really good observation — and it’s tied to how public form permissions currently work in Jira Cloud. Even though a form is marked as Public, Atlassian distinguishes between: Completely anonymous users (no Atlassian account), and Users who are logged in but don’t have Jira product access (e.g.,…

Hi @Kelwin Peralta This issue usually occurs because the custom fields you added aren’t linked to the screens used by your request type. Even though you can add them to a Jira Service Management form, Jira will automatically hide those fields if they aren’t included on the create, edit, or view screens for the linked issue…

Hi @Kristin I know there are some problems with attachments in software projects right now. Even though public forms in Jira Software or Business projects can accept submissions from anyone with the link, attachments are restricted for security reasons. Atlassian’s public documentation and community threads confirm that…

Hi @Timothy McKay If you ever need to update dropdown or multi-select options that appear in a Jira form, remember that Jira Forms simply display the options from their linked custom fields — they don’t store those options themselves. You can adjust those values by going to:Jira settings → Work Items → Custom fields →…

Hi @Reinbeaux.Leitch You’re right — the documentation you found refers to the “Form submitted” trigger, which is available for Jira Service Management (JSM) projects using advanced forms. However, in Jira Software projects, that specific trigger isn’t supported. Every form submission there simply creates a new work item…

Hi @Allen Han Jira’s native forms in Software projects currently have a fixed-width layout and don’t dynamically resize based on the browser window. The layout is optimized for consistency inside the issue view rather than full responsive behavior, so unfortunately there’s no setting or CSS customization available to…

Hi @Simon Hartshorn Even if you’ve set your form to “public,” JSM’s native forms aren’t truly accessible to non-licensed users unless they’re shared through the Customer Portal. Public form access in JSM only applies to portal visitors, meaning users who can access your service project’s customer portal — not the general…

Hi @Todor Krasimirov Tsekov Officially, Atlassian documents that every time a form is added, re-published, or cloned, a new form association ID is created for that issue. You can confirm the current field or form ID via the REST API: <span>GET <a…

Hi @Ismail Sanni This may happen in Jira’s native forms under a few conditions. When a form field is linked to a Jira field, the link between them can break if: The mapped Jira field was renamed, deleted, or its context changed (for example, removed from the project or issue type screen). The form was copied or moved…

Hi @Kathleen Hamilton In Jira Service Management’s native forms, you can use help text or field descriptions to show examples, but these currently only support plain text or basic formatting — embedding an image directly in the field isn’t available. If you want to include visual examples or reference images inside the…

Hi @Tatiana Torset Yes, sure, can you please tell me if it is internal(in your Jira instance customer) or external?

Hi @GlenellRosburg 1. Default Values You can use default values for some fields in native Jira or JSM forms (like setting "Client" = "All"), but: The user can still see and change the value. It works best if you're just trying to reduce mistakes, not enforce logic. 2. Smart Forms for Jira With Smart Forms for Jira,…

Hey @Yancey Larochelle-Williams 👋 This is a super common challenge — getting clean, structured input into your backlog without overwhelming your team or losing context. You’re right that each of your options has trade-offs: Forms in Jira Software are handy but limited — you can’t hide metadata like labels or capture where…

Hi @Dan Driscoll When you create a form with a public/external link, the email field you're seeing is typically used to identify the reporter/requester of the issue. However, this email doesn't automatically map to a custom field or appear as a separate field on the issue itself—it's usually just used to set the Reporter…

Hi @Mathew Lederman Atlassian has been rolling out native form improvements gradually, but dynamic/conditional logic in Software projects hasn't arrived yet. It's still primarily a JSM feature at this point. I'd recommend keeping an eye on the Jira release notes or the Atlassian roadmap for updates on when this might…

Hi @Joni Johnson I can clarify what's happening with JSM forms vs. Jira Software forms. JSM Portal Forms: You're correct that JSM has a feature called "Request Type Forms" where you can create form fields that are not custom fields. These are called "form-only fields" and they: * Only exist within the form itself * Are…

Hi @Jessica Abreu Native Jira automation doesn't have a built-in way to automatically download form attachments and send them externally. However, there are a couple of approaches you can take depending on your workflow needs. You might consider is using Smart Forms (developed by my team) with the "create new work item"…

Hi @Zachary Williams If your internal users just need to submit requests, fill out forms, or track tickets, you don’t need to manage them as full users or enable SSO (via Atlassian Guard). Here’s how you can give them access: Go to your JSM project → Project Settings → Customers You should already see users there (if…

Hi @Urmo JSM automation doesn't directly attach the submitted portal form as a visual file or formatted attachment in the email. The automation can reference individual field values using smart values (like {{issue.customfield_12345}}), but it won't recreate the form layout itself or generate a PDF/attachment of the…

Done:)

Hi @Jewell Sutton Great question — the “forms” concept can definitely feel a bit abstract at first, so let me break it down. Forms in Jira Service Management (JSM) In JSM, you can create forms and attach them to request types. They’re designed to be published in customer portal where after forms submissions work item will…

Hi @Stacey Steiger Welcome to JPD and thanks for the thoughtful breakdown - you’ve nailed one of the biggest gaps many teams feel when getting started: structured intake. You’re right that Atlassian’s current guidance leans on JSM intake or dedicated projects, but if neither fits your setup, another path you might explore…

Hi @NoName You’re not missing anything on your side — this is tied to how Atlassian designed request type forms vs. the issue create screen. That banner “This request type includes a form that can’t be seen in this view” used to appear when an agent tried to create a request with a form directly from the Create Issue…

Hi @Jens Schumacher - Released_so We just released the first version and are continuously improving it, and we truly believe in the potential of AI development. Of course, not all apps will simply stop working—but as Atlassian notes, if your app relies on a Connect module that reaches end of support, it’s effectively ‘use…

Hi @Bryan Guffey We just released the first version and are continuously improving it. As an Atlassian Marketplace app developer with experience building 10+ apps, we’ve brought our expertise in Atlassian app development to make the LLM better at delivering meaningful and usable output for Forge apps. We’re currently using…

Hi @Jimmy Seddon Thanks for the note! Just to add some transparency: if the app above creates a new Forge app for your company, starting Jan 1st, 2026, Forge will have a new pricing model:Forge Platform Pricing This means that if your app exceeds the included usage limits, your company will be responsible for any overage…

Hi @Matt Doar _Adaptavist_ This app is created based on your requirements in a prompt. Of course, everything depends on Forge’s capabilities — if a certain feature is currently missing, Atlassian allows you to submit a ticket for the missing Forge capability. If you believe any of these capabilities are critical to your…

Hello @Ulrich Kuhnhardt _IzymesCo_ Yes, any private Connect apps (custom apps not published on the Marketplace) will stop working if their functionality depends on features or updates that Connect no longer supports. Similarly, custom workflows or folders tied to Connect apps may also be impacted if the underlying app…