Comments
-
Do not use the database directly. It is not optimised or designed for reporting and you'll quickly find yourself trying to write hideously complex SQL that can become a performance problem and still not give you the data you need. Please, use the REST API for extracting reports - it's much more logical, faster, respects…
-
What is a "dump" of fields? What are you trying to compare? Data or configuration?
-
Depends on the mid-level version is (5.1 will be dropped this week, 5.7 around Christmas, etc, all of 5 dropped by next Christmas) See https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html - it's the policy and Atlassian put dates on to save us some time.
-
They were called "independent" for a while, but we don't use that much any more. They don't have the schemes the "classic" projects have.
-
You will need to check with the email admins - Jira simply sends an email to an email address, it does not know or care that a target is a user or a list. The reason I've often seen mails to lists or groups fail is because the mail server is configured to not deliver emails to groups or lists that are from automatic…
-
What do you mean by "quota"? Could you explain what the goal is of this - what does the end user get from it?
-
Jira does not have any scanning functions in it - you will need to find or write some code to do it. My instinct would be to have a small script that calls the software you scan with (as most of these can simply create files) and uses Jira's REST API to push the files in as issues.
-
You do realise this is not about Next-gen projects - it is about classic boards where you can add estimates on Kanban
-
There is nothing to "solve" - assignee is a single person by design, for the reasons discussed above. If you need to include other users, use custom fields to do it (also discussed above)
-
Jira runs on Tomcat, so there is a Tomcat starting up. Do you mean you are trying to start another Tomcat for something else after you've started Jira?
-
Take the field configuration you created and copy it. Go into the copy and make the "acceptance criteria" optional. Now create a new field configuration scheme and add both of the field configurations to it - using the new one for bugs (and other issue types that should not have the criteria field) Associate the new field…
-
The agent could "move" an issue from the service desk project to a developer's software project. But this would lose the request and from the customer point of view, delete their request. You should use "create linked issue" to create other issues for the developers to work on.
-
No. It's supposed to be a bit of text to tell us at a glance what the problem is. A dropdown is utterly useless as a summary. You would need to rewrite the whole of Jira to do this (and it would make the system pretty useless as an issue tracker)
-
What do the logs say the connection problem is?
-
Plain Jira (core) has only two sets of issue types - issues and sub-tasks. Issues are the heart of Jira, they represent "something that needs some attention". Sub-tasks are issues in their own right but have one big difference in that they represent part of a bigger issue, so they always have a "parent" that they are in.…
-
I'd still strongly recommend using a supported database. If you have any other problems, you'll need to before Atlassian will help you.
-
You can't, you deleted them. The admin audit log will tell you that a user was deleted, but you can't get information about the user - you deleted them, so it's all gone
-
The admin audit log will tell you that a user was deleted, but you can't get information about the user - you deleted them, so it's all gone
-
Whatever you did while "applying SSL" sounds like it has fixed it.
-
Could you explain what you mean by "aging" and what you want to put in front of the users?
-
I don't know, this sounds like a very specific problem and could well be a bug. But as it's failing, I would expect to see something in the log that tells us what is going on.
-
Start by moving to a supported database - MariaDB is not, so you need to swap to one that is.
-
This is a problem with Squid rather than Confluence, as Confluence is serving normally when you access it directly. I'm not actually sure what you're doing here because you say "Squid is configured to not proxy", but that's exactly what you should be doing with Squid in this case. If you're not using Squid for caching or…
-
See https://confluence.atlassian.com/adminjiraserver/managing-project-permissions-938847145.html - look for the manage watchers permission
-
Trello is not for knowledge bases, in my opinion. It's a transient list of stuff that needs attention or for memos, but it does not feel right for long-term storage of documentation or knowledge. A card can easily be edited, moved to a place it's hard to find, or deleted, and that's wrong for knowledge bases. For knowledge…
-
Go to the project admin and select the new workflow scheme which holds the association.
-
Please see the comments on the accepted answer (the community board has an outstanding request to "convert useful comment to a useful answer)
-
For most Jira usage, you create a workflow, reference it in a workflow scheme (these say "for issue type X, use workflow Y") and then associate the scheme with the project. The exception is Cloud "next-gen" projects, where your people set their workflow themselves. Could you tell us where you are stuck with the workflow…
-
Projects cannot be converted to Next-gen (or back) - you have to create a new project of the right type, and then use bulk-edit to move all the issues in to it.
-
There is no way to do this - a board is a view of a set of issues, not a defining feature. There is nothing wrong with having boards based on "label = X" (or not-X), but the board does not inform issue creation in any way. Your people don't care where they are when they create an issue, they just want something doing. I…