Earl McCutcheon Atlassian Team

Hello @Max Romaniuk , Currently the work ratio JQL function detailed at the bottom of the "Advanced search reference - JQL fields" documentation is what you are looking for but it is only avaliable for use in Classic Projects at this time as it requires the project to have Time tracking enabled to use the work ration…

Hello @Sasha K , Thanks for reaching out, and the error you encountered usually indicates an issue with the custom fields context settings or the global permission settings for the user running the call. First Check and verify that you have the "Administer Jira" Global permission, as covered in the API documentation for…

Hello @Somanathan Dharmarajan , Thanks for reaching out, and as a great starting point check out the following KB article that gives some recommendations on SLA tracking reports that can be leveraged for this: * Reporting on SLAs And additional high level breakdowns on the avaliable reporting options in "Discover new…

Hello @cuperman , The Development status endpoints to update the details are not exposed, check out the following Feature requests that gives some details on some avaliable GET options in the description and comments but there are not any exposed POST options and also note and be aware of the warning: There exists a…

Hello @Sanjeevani_Chaudhari , The Time tracking fields on the issue view directly, Estimated, Remaining, and Logged, should be displayed as a progress bar and the time estimate that sounds like what you are describing, like this: Are you by chance talking about the Progress bar in the time tracking report as detailed in: *…

Hello @Sunil Singh , It looks like you are following the path of looking up the meta-data for creating issues as detailed in this developer documentation: * JIRA Developer Documentation : JIRA REST API Example - Discovering meta-data for creating issues However, Following the method described above you would want to…

Hello @cuperman , If an app is broken and does not work we will work witht he vendor to apply repairs and get it in a working state but it would be removed if not possible. The App approval Guidelines and Vendor Agreement can be seen at the following links: * App approval guidelines * Atlassian Marketplace Partner…

Hello @cuperman , The Support contact details for the add-on app can be found on the support tab of the marketplace listing here: * https://marketplace.atlassian.com/apps/1220515/azure-pipelines-for-jira?hosting=cloud&tab=support The direct links are: * Email vendor * Submit a support request * Go to vendor status page…

Hi @Frank Mingbo Li , Thanks for pointing this out, and the Search Dialogue is only visible in the Backlog in JIra server. I created the following Feature request to follow up and align the behavior between the cloud and server platforms, make sure to add a vote to the request to show your interest, and feel free to add…

Hello @Steven Choiniere , It sounds like the Epic has been closed out via the epic Status Field being set to done. Epic Status and Status are independent of one another, so if the Epic is in an open status but missing from the board and reports, in order for the Epic to disappear from the board, you must mark it as Done…

Hello @James N_ , Thanks for reaching out and from the behavior you described It sounds like there may be an exclude happening on the issue status or on one of the fields being set on the transion in the boards filter. Go to the "board configuration > General" and look at the "Filter Query" and the "Kanban board…

Hello @Rohit_Jindal , To move data between Next-Gen and a Classic Project you will want to use the Bulk move operations not the CSV export and import from the source project to the destination project as there are going to be conflicts in the field types. The process is detailed in the following Knowledge Base article: *…

Hello @dhrupkumar , There are some major changes in place that is part of user privacy changes for GDPR compliance that obfuscate all usernames and Emails and they have been removed from the API endpoints and replaced with the account ID and tying them together from external sources is intentionally blocked as part of the…

Hello @Thi Tran , Thanks for reaching out and as a referance point Details on creating a new project can be seen in the following documentation: * Create a project in your new Jira experience And you noted having admin permissions, so if you do have global admin the option to create a project should be visable in either…

Hi @stadlerm , As covered in the KB's above: The following custom field types are supported: * checkbox * date picker * user picker (single user) * number * radio button * label * single-choice select * multiple-choice select * single-line text * URL (read-only) So if an app has created and is using a custom field of one…

Hello @Alexander_Tanno , Currently this is a hard set limit, and the roadmap shows a maximum of one year into the past and two years into the future based on a starting point of today's date (current day). We have the following Feature request in place to track interest in extending this limit, make sure to add a vote to…

Hello @Evgeniy , Jira service Desk has two separate mail handling processes, One for internal communications for agents and internal users and the other for customer facing actions. A full detailed breakdown on how the service desk notifications can be see in the KB: * Jira Service Desk notifications in-depth When someone…

Hello @John Ritchey , The Maximum value allowed in the story point field is capped really high at a value of '100000000000000', which can be seen in an error displayed if you attempt to overload the field: However I would highly recomend against against going this high as it would become harder to manage as you get to…

Hello @Rabona Corporation , Thanks for reaching out, and this does look buggy, However I took a look at this and I was not able to reproduce this behavior in my test instance, so there has to be something either locally blocking this (i.e. browser issue) or a configuration difference between the systems triggering a bug. I…

Hello @Carol Rigdon , Thanks for reaching out, and details on editing a sprint can be found in the following documentation for a referance point under the section "Editing, reordering, or deleting a sprint": * https://support.atlassian.com/jira-software-cloud/docs/plan-a-sprint/ And the Sprint start and end dates can be…

Hello @Martina Bobotilova , The error you encountered lines up with the following Bug: * https://jira.atlassian.com/browse/MIG-95 The Bug is noted as having been fixed in the last few days so you should be good to go with a new export file. Can you generate a new site export from your source Jira instance and try again and…

Hello @Anand_G , Thanks for reaching out and there should not be any difference in the Free tier for importing issue via CSV. As a referance point the formatting for importing a subtask can be seen in the following documentation: * https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html And…

Hello @Fred Lumiere , If you have applied a rule to a project, and then modified the rule at a later time, to revert to the default rule you can delete the modified version and add a new rule from the template or revert the changes applied manually. The default rule from the template "Triage Email Requests" is: * When this…

Hello @Saikiran Bommerla , Currently it is not possible to copy attachments using automation for Jira on the Cloud platform. The addition of this feature is being tracked here: * https://codebarrel.atlassian.net/browse/AUT-1030 Regards, Earl

Hello @Vineet Bansal , As a referance point the Add comment syntax can be seen here: * POST /rest/api/3/issue/{issueIdOrKey}/comment Then the error you noted is indicating that the "Body" section is missing, {"errorMessages":[],"errors":{"comment":"Comment body can not be empty!"}} Try updating the syntax in your a.json to…

@LarryBrock , you just made me spit some coffee on my desk because i could not hold back the laugh...... Good one :) 

Hello @Pascal Steinhoff , Thanks for reaching out, and currently for Next-Gen projects the create Epic is not avaliable at this time. We recently added in options for creating issues in the epic or adding issue to an epic that already exists via this feature request, but the creation of the epic itself is not yet possible,…

Ahhhhhhhh man I love my self some breakfast foods, But i actually have never been a big breakfast at breakfast time person, I prefer to eat a small meal in the AM maybe a piece of toast or a granola bar. BUT i regularly do a Breakfast for Dinner or a fancy lunch with brekkie foods and man can i make a mean pile of…

Hello @Alexandru Muntean , I'm taking a look at your request but just a heads up I noticed that your API token was in plain text in the CURL output you posted, I edited the post to remove the sensitive content, But I highly recomend for security reasons revoking the API token and creating a new one as this is a publicly…

Hello @Jean Coudert , Thanks for reaching out and looking at the example you are using the syntax looks formatted as a SQL style database query, from this KB: * How to identify group usage in JIRA But, this only applies to a Jira server instance and is run from the database directly on the systems backend, If you are on…