Belto Atlassian Team

Both the Start date and Due date are calculated simultaneously with the auto-scheduler which looks at the totality of all assigned work items and schedules for not just when they can be started and ended meaning that no 1 work item (issue) is scheduled independently and multiple items can start and the same date. The…

This is the Quick filter feature which is not available on the Backlog view on the mobile version of Jira Cloud. A feature request has been raised for this to be included in the view in JRACLOUD-73536 .

@Vincent Mutambuki { Mumo Systems } If you're having trouble importing a JSON file I recommend raising a support request at support providing the file being used and specifying what exactly isn't working (errors, failure, ect...)

I can totally understand. Instead of disabling the wiki markup, you can try the workarounds mentioned on JRACLOUD-72429 / CONFCLOUD-67922

If you wish to disable the smart link feature altogether from the comments in Jira you can modify the renderer from Wiki Style Renderer to Text Renderer. https://confluence.atlassian.com/adminjiracloud/specifying-field-behavior-776636443.html Also dropping the bug ticket for this here:…

Amongst all the available reports for Software that keeps track of scope changes, the Burnup Chart, Epic Report and Epic Burndown are good solutions.

https://jira.atlassian.com/browse/JSWCLOUD-17240

The Scope view does not take into account closed Sprints. To have more control over the future, past and current Sprints, you will have to use the Scope filters to define over what period of time the Plan should look at. See Using scope filters for more details.

@Barry Rudlin Unfortunately not, by adding yourself as a watcher to the bug report you will receive all communications done on this and updated once fixed.

This happens due to having a high volume of Epics on a Project. This bug was reported recently in JSWCLOUD-17538 and our Developers are actively working on this for a swift resolution. Regards.

Issue was resolved by the user by correcting the following: 1. Ensuring that referred statuses have no surrounding whitespace. 2. Exactly matching every letter - including case - to existing statutes. If one is inaccurate, the entire import fails. 3. The exported data treated arrays/lists almost unconditionally as…

A miniature 3D printer would be a great gift for a creative mind (why buy toys when you can 3D print your own :P ?).

That is correct James ;). Only licensed users (users with product access) are counted and billed.

Users who do not have product access won't be counted towards the licensed users. As agents, without having product access they won't have access to the knowledge base. As customers (portal user), they do not require product access and are able to access the knowledge base if configured that way in the Project settings.

Currently, there is no way to disable who can Start a Team. * https://confluence.atlassian.com/cloud/teams-in-atlassian-cloud-958446984.html

We do indeed have a public facing documentation where all our public APIs can found : JIRA Cloud REST API There isn't an endpoint for deactivating users but there is one available for removing them which is still in its experimental phase: Remove user EXPERIMENTAL DELETE /rest/api/2/user Removes user. Request QUERY…

It sounds like you're trying to change the email via id.atlassian.com. Because the user is managed by Google the email change can only be done directly in Gsuite by the Gsuite Administrator. Changing user details in Gsuite The impact of changing the email of the users in Gsuite is that the email change will sync with their…

See the response given in Can I restore a Sprint? which answers this question

To my knowledge, this is only achievable by writing a script to update the field with a date calculator using the ScriptRunner for Jira third-party plugin. However, if you're simply looking for the Due date field to be set this indeed achievable. There are different ways of going about this but the most effective I can…

As a JIRA Administrator, you can change the default language by clicking the "Edit settings" button on that same page in the screenshot (General Configuration). See Choosing a default language for instructions.

This is a bug that is now fixed in JIRA server (https://jira.atlassian.com/browse/JSDSERVER-4968). Jira cloud users are experiencing this and a fix for this bug is currently in progress (https://jira.atlassian.com/browse/JSDCLOUD-5764).