Gor Greyan Expert

Hi @Harshad Prajapati Welcome to the Atlassian Community! I think it only exports active, licensed users or users within a specific directory/group, not all users in Jira. I’d recommend checking if the missing users are: inactive/deactivated not assigned to the application coming from a different directory or group not…

Hi @Jonnie Bloor Welcome to the Atlassian Community! Yes, this is possible, but it depends on your board configuration. Epics appear in the Epic panel based on the board’s filter (JQL), not where they were created. If those epics are not showing, it usually means they don’t match the board filter. Once they are included,…

Hi @Asier Vadillo Great, I saw it. Thank you, too.

Dear @Tijoriwalla_ Prashant Kindly ask you also to accept the answer :)

Hi @Tijoriwalla_ Prashant Welcome to the Atlassian Community! In the attached screenshot you can find the Activity part, from where you can choose from the dropdown the "History", which will show transitions and field changes. Or you can choose All to see all the history for that story. Let me know if you have any…

Hi @Asier Vadillo Thanks for the question. Am I right that you want to set a validator on the transition, where the screen is being displayed, or do you want to set a restriction, if the assignee is empty or not a Bot, the transition is not being displayed at all?

Hi @Anna Urbanska Welcome to the Atlassian Community! This is most likely due to the Jira issue view UI changes, where some apps are no longer automatically displayed in the main view and are instead accessible via the Apps/Automation panel or by manually expanding them per issue. I think there’s no native setting to force…

Dear @Phillip Guardiola Well, let me know if you have any questions.

Hi @Dave L_ Welcome to the Atlassian Community! This is controlled by Atlassian Access mobile app policies—admins can enforce a minimum OS version (in your example, Android 13), which overrides the app’s general requirements. See this documentation:…

Hi @Phillip Guardiola I would treat this as two separate things: First, the error text points to Jira failing internally while resolving custom field mappings, which is why it looks intermittent and is something that I think Atlassian Support can investigate. Second, your request format is worth correcting, because…

Hi @Eric Blankenship Welcome to the Atlassian Community! I think this learning course will help you. https://community.atlassian.com/learning/path/configure-agile-boards-for-jira-projects Also, you can explore more courses here. https://community.atlassian.com/learning/catalog?search=board&product=Jira

Dear @Prasanna Subramaniam You can just use this without a custom field. Just Edit work item and put the following JSON. { "update": { "labels": [ { "add": "SL_{{issue.sprint.size}}" } ] } }

Dear @Prasanna Subramaniam customfield_10020 is the number field, which you have created and kept there, the {{issue.sprint.size}}?

Dear @Prasanna Subramaniam There is no native JQL, which I could find for sprint count, and ScriptRunner doesn't have any function that can return the sprint count for that issue. Only my mentioned option, I think, can work. Keeping the sprint size in the custom field, then try to retrieve it via JQL, searching that custom…

Hi @Prasanna Subramaniam Welcome to the Atlassian Community! Adding, what @Marc -Devoteam- said. That will also return those stories, which were only in one sprint. If you need an exact stories, that was gone through multiple sprints. You can add a number field in your stories, and run an automation with this smart value,…

Hi @Carolina Godinho Welcome to the Atlassian Community! As I researched, Xray doesn’t support inheriting fields from a Test Plan to a Test Execution out of the box, as they are separate issue types. If you need this behavior for copying Fix Version, you can achieve it using Jira Automation by triggering on Test Execution…

Hi @Usman Sharif For information on organization deletion, see this article. https://support.atlassian.com/organization-administration/docs/delete-your-organization/

Hi @oranos dawar This happens because Atlassian requires every site to have at least one billing admin, so if you’re the last one with that role, your account can’t be deleted while active subscriptions still exist. Since you don’t have access to the site, you’ll need to contact another org/site admin to either transfer…

Hi @Karolina Didikaite Welcome to the Atlassian Community! You can check this documentation. https://support.atlassian.com/jira-cloud-administration/docs/data-limits-and-guardrails/ This doesn’t mean you’re limited to 50 users or 18,000 issues.The 50 limit only applies to a single permission entry (i.e., how many…

Hi @PEDRO SANTANGELO CALVO Thanks for the question. I could find the following KB. Please have a look on this, maybe help you. https://confluence.getxray.app/display/public/XPORTERCLOUD/Exporting%2BTest%2BExecution

Hi @ckopanon Thanks for the question. Natively, Jira doesn't have trigger for the Tempo log time, but if you have ScriptRunner, I think we could do it with ScriptRunner's Listener.

Hi @Walter_ehrenhard Welcome to the Atlassian Community! I think that this behavior usually means the Activity Timeline app is interpreting dates in UTC rather than your Jira user's timezone. Even if your timezone is set to Europe/Amsterdam, the app may apply its own configs. Did you check the app’s documentation for any…

Hi @Patrick Fournier Welcome to the Atlassian Community! The Organizations field isn’t a standard select list—it’s a special JSM field that already lets you pick from existing organizations. However, Jira doesn’t support using those organizations as options in a custom select list, so you can’t replicate that behavior…

Hi @Satyam Mooloo Welcome to the Atlassian Community! You should have 2 automations. 1. Issue Creation Trigger: Issue Create Condition: Labels contain COS<br>Action: Create an issue in Space B Branch Rule: Most Recently Created Issue Action: Add Issue Link (e.g., “relates to”) 2. Issue Update Trigger: Issue Updated in…

Hi @Dieter Guthmann In the Jira Cloud, there is no native way to pre-fill the Watchers field on the issue create screen, as watchers cannot be set during issue creation via the UI. The most practical and commonly used solution in Jira Cloud is to rely on automation rules to automatically add a predefined list of watchers…

Dear @WW _ 정유정 If the answer helped you, kindly ask you accept the answer. Have a good day.

Hi @WW _ 정유정 Thanks for the question. When you move from Jira Data Center to Jira Cloud, you cannot continue using your existing Zephyr Essential (Data Center) license because Atlassian Marketplace apps are platform-specific, meaning Data Center and Cloud versions are treated as separate products with different licensing…

Dear @Carles Mata Glad that could help you. Have a good day :)

Dear @Crystal Miller No problem, glad that @Tomislav Tobijas provided the ticket link, where the issue is reported. Have a good day :)

Hi @Alec Keeler Thanks for the question. Check the APIs documentation, I think this will help. https://developer.atlassian.com/cloud/assets/rest/api-group-object/#api-object-id-put