Olha Yevdokymova_SaaSJet Atlassian Partner

Hi, yes we work with assets and we support advanced conditional logic with multiple conditions and condition groups so you can reveal fields dynamically. Also Smart Forms have api data soure for the form responses.

Hi! It looks like there may have been some confusion in the previous response between different Jira field limits. For a team-managed JSM space, the 50 custom field limit can still become a real constraint. If you’ve reached it, there are a few ways to handle this: 1. Reuse global custom fields. Team-managed spaces can use…

Hi @jverdoza I think the tricky part here is that public visibility and customer account creation are still tied together in Customer Service Management. For a Customer Experience to be accessible to anyone without logging in, Atlassian currently requires the global customer-access setting to Allow customers to create…

Hi @Joshi As @Tomislav Tobijas mentioned, this isn't currently available directly in native Jira Forms. The feature request JRACLOUD-94094 is still open, so using Jira Automation to send the reporter an email with {{issue.key}} / {{issue.url}} is probably the most practical native workaround for now. If you're open to…

Hi @klevenick2 Yes, this is a tricky one because there are really two layers here: the form knows which attachment was uploaded for which question, but Jira ultimately stores the files together in the standard Attachments field. With native JSM Forms, you can at least reference an attachment answer from a specific form…

Hi @Darryl St_ Pierre There are two slightly different things involved here: the attributes stored on the managed Atlassian account and the newer Customer Service Management customer detail fields. For managed accounts, Atlassian does support syncing attributes such as Department and Job title from your identity provider.…

Hi @Ray Stone You're not missing anything — the reuse in native JSM is mainly at the whole-form level, rather than letting you build a request from several reusable form modules. And I agree that a modular approach would make a lot of sense for cases like HR, where the same blocks of information appear again and again. If…

Hi @Rick Austin Given the workflow you described, another approach you might consider while Atlassian is evolving the native JPD experience is Smart Forms for Jira, developed by my team. I wouldn’t position it as a replacement for JPD — JPD can remain the source of truth for prioritization, roadmap decisions, and delivery.…

Hi @Jye Barber As Divya mentioned, native CSM forms currently can’t be embedded directly into an external website. If keeping the whole experience inside your website is important, another approach you might consider is Smart Forms for Jira, developed by my team. Smart Forms can be shared externally and embedded directly…

Hi @Keith Jones That explains it — having deleted custom fields with identical names still in Jira’s temporary deletion period would definitely make this difficult to spot. Since you mentioned you have several automations following the same pattern — create another work item → attach the same form → copy ~30 values —…

 Hi @C0666379 I think the tricky part here is that you’re having to work with the internal ID of a Jira Forms question, rather than with a stable field identifier. If you’re open to an app-based approach, Smart Forms for Jira is developed by my team at SaaSJet, and we handle this a little differently. Smart Forms has a…

Hi @Shakira Davis Heath Adding to Trudy and Marc’s answers — the exact behavior depends on whether you’re using Jira Service Management or a regular Jira project. With JSM, customers can receive the standard request confirmation through customer notifications. For regular Jira projects, as Trudy mentioned, you can use Jira…

Hi @Nadir Jabbarli Currently this is Cloud only, but it is super easy for our team to make the same functionality on the Smart Forms DC version, the only reason why its not here - we got no feature requests for it.🙂 So in this case you can get an app trial, see if it fits for your needs overall and than submit feature…

Hi @jack_verstappen Dan and Gabriela have outlined the two main native approaches. You can add the partner’s users as customers in each customer organization they are authorized to represent. When raising a portal request, a customer who belongs to multiple organizations should be able to choose the relevant organization…

Hi @Andreas Gandrup Jira Automation cannot currently react when someone opens the native + Create dialog, so it cannot dynamically inject values into that screen before the work item is created. Another approach you might consider is Smart Forms for Jira, developed by my team. It would not modify Jira’s native creation…

Hello @Kinza Jabeen James’s approach is the right starting point for native Jira Automation: copy attachments and compatible custom fields during cloning, then use a separate comment-sync rule with safeguards against loops. The main complication is the form data. Jira treats form-only responses separately from standard…

Hi @Kathryn Lee Jira does not currently provide a native dropdown of reusable Story templates that can prefill several fields differently for each recurring process. Native Jira forms can create work items from submissions, but they work more like structured intake forms than selectable issue templates. A practical…

Hi @Oliver Christie Atlassian’s documentation doesn’t currently describe support for using Slack Workflow Builder’s Create issue step to create JPD Ideas and map a complete Slack form into JPD fields. That would explain why the same step works with a Jira Software project but not with your JPD project. Another approach you…

Hi @Andy Fieweger The Create idea form isn't configured field-by-field. Instead, it's driven by a view. When you go to + Create → Configure form and pick your idea type, you'll see it's tied to one of the views in your space. Whatever fields are present in that view become the fields on the Create form — which is exactly…

Hi Florian, You may try Smart Forms for Jira developed by my team, there are Regex validation for attachment field, which may help you validate the file type. There are also possibility to add several attachment fields with different file types validation.

Hi @Spandan Depends on the app and its purposes, but in my experience inbound marketing works the best, try to solve real problems and create content around your topic, all content types and differnt channels as well cause it depends mostly on target audience, check communities with your target audience, leverage linkedin…

Hi @GOVIND K_ For the requirements you listed, Jira Service Management is the natural place to start. It already covers many core ticketing portal needs: email-to-ticket creation, customer portal access, queues by department, agent permissions, internal notes, customer notifications, SLA configuration, business hours,…

Hello @Sharon Halpin Glad that you have a good experience with our support team, but if you will still need something you can also book a demo or ask for a guided loom video for your exact case🙂

Hi @Dennis Gomez Hernandez Yes, this is possible in Jira Service Management. For the usual customer-facing flow, you do not need to build anything from scratch. JSM has built-in Customer notifications, and one of them is sent when an agent adds a public reply to the request. This notification goes to the Reporter/Requester…

Hi @Abilash Arkadiusz is right, the first thing to check is which attachment field you are trying to use. In JSM Forms, there is a difference between: * the native Jira/JSM Attachment field * the Attachment field available inside the Forms builder The native attachment field belongs to the request/issue itself, so you…

Hi @Sharon Halpin For the native Jira Issue Collector, required fields are quite limited. The collector does not really work like a full form builder where you can mark each field as required directly in the collector settings. The required behavior usually comes from Jira field configuration. So if a field is required in…

Hi @Jean-Michel Garcia If the work item is created successfully until you add the Slack multiple-choice answer, then it is probably not a required-field issue. It sounds more like a formatting/data type problem between Slack Workflow Builder and Jira. Multiple-choice answers from Slack are often passed as a structured…

Hi @Akzhan Tynymbay In Jira Software projects, the native Forms experience is usually focused on intake - meaning the form submission creates a new work item. The “Add form” option on an existing work item is generally associated with Jira Service Management forms / legacy ProForma behavior, so it is not be available…

Hi @Sargun For a Jira Software project, this isn’t really possible with the native Jira form functionality today. Native forms are fairly limited when it comes to using conditional logic for dynamic guidance text or changing descriptions based on earlier answers. One workaround you might consider is Smart Forms for Jira,…

Hi @Robert In short: on JSM Cloud there is currently no native setting that allows email-based customer support while completely removing authenticated customer portal API access. The choice is generally between allowing portal customers, disabling customer support access entirely, or implementing an alternative…