Comments
-
I would advise training or helping your team leads to do their job better. If they are trying to use numbers in the issue tracker to look at how individuals are performing, they clearly do not understand what the team is doing. A good team lead will not need to see numbers, they will be working as part of the team, and so…
-
Welcome to the Atlassian Community! "Access to Jira" usually means "I can log in and look around". Your access to the projects and issues within any Jira is controlled inside that Jira. I would assume that while you can log in, you have not got access to the projects you need inside Jira. You should talk to the project…
-
Welcome to the Atlassian Community! No, you will have to handle your own distribution of costs internally. Atlassian simply bill one organisation for the use of their systems.
-
There is no use for a support.zip on Cloud - Atlassian have direct access to your system and don't need it. The system logs don't capture most change though, so they would probably not tell you anything about the changes that were made. System logs are more about the running of the service, not data change. The audit log…
-
Yes, as I said, it's an issue tracker - the whole point is that it keeps a history of change to issues (including who performed the change)
-
Jira is an issue tracker. It tracks almost all change, as it should. (I only say "almost" because it doesn't have proper change control on comment edits or issue deletion, which I always turn off)
-
Welcome to the Atlassian Community! Sprints do not have a "schedule" beyond "the team plans what they are doing". There's no restrictions here, it's allowing a self-organising team to respond to what your organisation needs.
-
Welcome to the Atlassian Community! The short answer is that "you don't". Workflows are variable. As soon as anyone edits a workflow (and one of Jira's greatest powers is that you can), you have a change that you can't guess reliably that has moved away from the defaults. There are no things like "RESOLVE_TRANSITION" or…
-
We might be able to give you a bit more if you could tell us what the logs say the problem is?
-
Welcome to the Atlassian Community! Yes, you will need to pay for everyone. Cloud is a subscription, not a licence model. This means the whole system is on one single subscription. Everyone is free, or all starter, or all standard, or all premium. (I will not bore you with "enterprise" at this point)
-
Welcome to the Atlassian Community! This sounds like it is all down to your authentication, so you'll need to talk to your database admins and how they want you to connect. There are guides for using many databases with Jira, albeit only the supported ones.…
-
Welcome to the Atlassian Community! Jira is an issue-tracker, not a document/file tracker. I would recommend * Improving your naming schemes so that files have more useful human names * Putting your file tracking into a file tracker, and linking it to issues There are some good apps in the marketplace that can help you…
-
Welcome to the Atlassian Community! Filters do not belong to dashboards, boards, projects, or subscriptions. They are independent items that can be used by many different parts of the system. There's no relationship Jira could give you between a dashboard and a subscription - if your subscription to a filter that was used…
-
Welcome to the Atlassian Community! They don't want to have to guess at and then provide for every possible customers. You can add your own custom date fields, and do with them what you want.
-
Are your custom date fields definitely date (or date/time) fields? Last time I saw this, they had added dates as strings.
-
Welcome to the Atlassian Community! There's a general principle in how Scrum, Kanban, and other things provide issue-tracking that fits well with Agile. Think of a board as representing a team. (Jira Align goes further - the board IS the team, end of story!) In Jira, a team is a view of a set of issues, not a container…
-
Welcome to the Atlassian Community! Those docs are about two different things. The first one is the end of support by Atlassian for doing support on a migration. If you're not in the end phases of a migration by November, you've left it far too late. Server support ends in February, not migration support. You can still do…
-
Team-managed projects do not have security schemes. Company-managed projects are created by admins, and the configuration of them (including security schemes) is done by admins.
-
Welcome to the Atlassian Community! This won't work - you don't really only have one team here, you've got two, and boards and sprints represent teams. If you really want the sprint reports to work, and only have one team, then you can't have "development done". The whole team needs a single definition of done, which means…
-
Have you read www.trello.com ?
-
https://docs.adaptavist.com/sr4js/latest/features/behaviours/behaviours-examples/field-level-permissions is pretty close to what you need already.
-
You have created a condition on it that says "don't do this for project administrators". Project administrators are the people who maintain the versions!
-
Welcome to the Atlassian Community! The easiest way to do this is to use Confluence's structure. * Create a space, and let your AWS users into it. * Remove all their access to all but that space * Move the stuff you want to share with them into that space * You can then use page restrictions within that space to hide pages…
-
The only way to recover disk space from attachments is to delete attachments, best done by deleting issues. (You could delete them from the disk, but then you just get an unclickable little "broken file" icon in your Jira issues) If you need to keep them, then your only option is to increase disk space.
-
Welcome to the Atlassian Community! I'm afraid Scriptrunner for Cloud does not support Request screens yet, only the global issue create screen. Also, the fields it supports are limited (the list is a little way into the docs at https://docs.adaptavist.com/sr4jc/latest/features/behaviours )
-
Welcome to the Atlassian Community! Versions do not have any concept of "current", unless you map it on to "unreleased versions", there's nowhere to tell Jira which ones you think are current. Your queries with unreleasedVersions and earliest/latestUnreleasedVersions are probably the closest you are going to get. For the…
-
Sorry, I keep forgetting most of my dev systems are altered in order to create those logs. You need to be reading the output from "atlas-run" as it compiles and builds your app, then fires up a Confluence. Some important points: * That log will end with "Tomcat started" in most cases, but that's the container not…
-
The "red brick" one listed in Sayed's link abovein one place, and a few on Spectrum
-
It will know to map the old accounts to the new ones if you map them in the JCMA.
-
Welcome to the Atlassian Community! You need to talk to Atlassian support, not the Community - we have no sight of Atlassian''s billing systems. As you have said "Trello", the best option is to go to contact support from https://trello.com/contact - make sure you use the last option on the page, the others will take you to…