Maybe this could work by configuring Assets? "Import your data into Assets" https://support.atlassian.com/assets/docs/import-your-data-into-assets/ I found the above, but then decided to ask Google Gemini your question too. This is what it said. The gurus here may be able to expand or eliminate these as options: "Yes, this is absolutely possible. Since you are looking to avoid direct database connections due to firewall restrictions, using a CSV as a middleman is a common and effective strategy. The Shared Data for Jira Fields app (by codefortynine) is specifically designed to handle this. You can host your CSV file in a cloud location that the app can reach via a URL, which bypasses the need for the app to 'touch' your internal Oracle systems directly. The Recommended Workflow Instead of a direct database connection, you can set up a 'push-pull' architecture: 1. Generate In-House: Run a scheduled script in your local environment that queries your Oracle/Data Warehouse and exports the required data (Email, Org Code, Dept) into a CSV file. 2. Upload to Cloud: Have that same script upload the CSV to a cloud storage service that provides a direct download link. 3. App Configuration: In the Shared Data for Jira Fields configuration, set the Data Source to 'URL.' Point it to your cloud-hosted CSV. 4. Field Mapping: Map the CSV columns to your Jira custom fields. You can set the app to refresh this data periodically (e.g., every hour or once a day) so your JSM tickets always show the most current customer info. Alternative: JSM 'Assets' (Standard/Premium Feature) If you have JSM Premium, you might not even need the third-party app. You can use the native Assets (formerly Insight) feature: - Import via CSV: Assets allows you to import CSV files from a URL on a schedule. - Object Mapping: Each row in your CSV becomes an 'Object' (e.g., a 'Customer Profile' object). - Ticket Integration: You can then use an 'Assets object' custom field on your JSM tickets. When an agent opens a ticket, Jira can automatically link the correct profile based on the reporter’s email, displaying their Dept and Org Code instantly.

I have not tested this, but this Marketplace App by Multiplier looks like what I would test out: https://marketplace.atlassian.com/apps/1224807/access-management-iga-for-jsm-okta-azure-ad-entra-sso

Atlassian says when outlining subtasks or tasks, "Decide which specific steps need to be completed and who is responsible for each of them." See: "How to write user stories" - just over halfway down this page: https://www.atlassian.com/agile/project-management/user-stories Furthermore, Atlassian says subtasks "allow you to assign different aspects of a work item to different people." See "Create a subtask or child work item" - halfway down this page: https://support.atlassian.com/jira-software-cloud/docs/create-a-work-item-and-a-subtask/ No matter the structure of the work, planning first, then providing clear intent and coordinating instructions to the team is paramount. Also, don't plan in a vacuum. Use the team! You guys are awesome, by the way! Thanks Alex and Josh!