--- title: "BigPicture Workflow Transition Limitations with Jira Transition Screens" canonical: "https://support.appfire.com/space/SUPPORT/3504079149/BigPicture%20Workflow%20Transition%20Limitations%20with%20Jira%20Transition%20Screens" format: markdown --- In BigPicture/BigGantt, *workflow transitions that use a Jira Transition Screen* are *not fully supported inline* in app views (Gantt/Scope/Board). As a result, the transition may be missing, appear blocked, or require the user to open the issue in Jira to complete the action. This may be confused with a BigPicture permission problem, but it is usually *workflow configuration / Jira UI dependency* rather than Box/App role settings. --- **Symptoms / customer-reported behavior** Customers typically report one or more of the following: - “The transition exists in Jira, but I don’t see it in BigPicture.” - “Other transitions work in BigPicture, but this one does not.” - “When trying from BigPicture, I’m forced to open the issue in Jira.” - “This transition opens a dialog / requires fields (transition screen) in Jira.” --- **Primary cause (known behavior)** Transition uses a *Jira Transition Screen* If a workflow transition is configured with a Transition Screen (i.e., Jira opens a dialog/screen to collect required fields before completing the transition), BigPicture may not be able to render/execute that transition inline in all views. *Expected outcome:* - Transition may not be offered in BigPicture, or - It may be offered but cannot be completed without going to Jira, depending on the view/context. --- **Quick triage (ask these first)** 1. *Can the same user execute the transition in native Jira?* 2. *Does the transition have a Jira Transition Screen configured?* 3. *Does the transition require any mandatory fields or validators that are collected via the screen?* 4. *Does the problem affect only one transition (while others work in BigPicture)?* If (1) is yes and (2) is yes, treat it as the screen-based transition limitation. --- **How to confirm (support steps)** Ask the customer/admin to confirm the transition is screen-based: 1. In Jira, open *Project settings* → *Workflows* (or workflow editor). 2. Locate the transition. 3. Check if a *Transition Screen* is assigned to that transition. 4. Provide a screenshot showing the transition configuration (or the screen mapping). If possible, also ask for: - Workflow name + transition name - A screenshot of the Jira transition screen configuration - A short screen recording showing: transition works in Jira but not in BigPicture --- **Resolution / Workarounds** Because this is a UI/inline execution limitation, the practical options are: h3. Workaround A (recommended): Perform the transition in Jira - Instruct the user to open the issue in native Jira and execute the transition there. - This is the best option if the screen is needed to collect required data (mandatory fields/validators). h3. Workaround B: Simplify/remove the transition screen (if business allows) If the customer needs to perform the action from BigPicture: - Remove the Transition Screen, *or* - Simplify the screen so it does not require interactive field input at transition time - (e.g., move fields to an Edit screen, relax required-field validators, or redesign the workflow step logic) Important: This is a workflow design decision for the customer’s Jira admin. --- What *not* to misdiagnose Don’t treat this as a BigPicture Box permission issue by default If: - Other transitions work in BigPicture, and - The missing one is the only problematic one, Then focus on workflow transition configuration first. BigPicture permissions still matter, but they are a separate layer BigPicture security roles (App/Box roles) govern what users can do in the app, but BigPicture still respects Jira’s ability to transition issues. For an overview of BigPicture security roles, reference: [https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211580061](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211580061) (source: ContentReadTool) --- Suggested customer-facing reply (template) This behaviour matches a known limitation in BigPicture/BigGantt: workflow transitions that use a Jira *Transition Screen* are not fully supported for inline execution from BigPicture views (such as Gantt/Scope/Board). If the transition requires a screen (dialog) in Jira, the recommended workaround is to perform the transition directly in Jira. If the transition must be available from BigPicture, the Jira admin may consider removing or simplifying the transition screen (depending on your workflow requirements). If you can share a screenshot of the transition configuration showing the assigned Transition Screen, we can confirm this applies to your case. --- **Information to collect (for escalation or confirmation)** - Jira Cloud site URL - BigPicture app version (if available) - Affected view (Gantt / Scope / Board) - Issue key(s) - Workflow name and transition name - Confirmation whether the transition has a Transition Screen - Screenshots: - Transition configuration (screen mapping) - What the user sees in BigPicture vs Jira - Any validators/required fields on the transition --- **Internal support notes** - If the customer reports “it works in Jira but not BigPicture,” always check for a Transition Screen first. - If the transition has *no* screen and still doesn’t appear, then proceed to secondary causes (e.g., workflow conditions such as “User is in Project Role”, app access context, caching). Keep that as a separate troubleshooting branch/article.