Comments
-
You will need to give more detail. One line doesn't tell us much. Although that one on it's own would make me suspect you've got a corrupted database.
-
Not that I'm aware of, it's just not coded for. Because once your Jira is configured correctly on a system level, you should not be messing with it. It's rare to need to change the system files, they're definitely not things you should be "hot swapping"
-
They'll get placed in the log directory. <application home>/logs/
-
This breaks your Jira system because you are amending things that are in a state of flux. A post-function is part of a transition. If you try to transition the issue again from within that, Jira gets very confused because you've changed your mind about the end state halfway through, and what you're trying to do might have…
-
You'll need to read the logs to find out what the "internal server error" is - the logs usually have a lot more detail. <jira home>/logs/atlassian-jira.log is the one to start with.
-
You can add more projects by amending the board filter so that it draws in the other projects. But it will remain two lines, as it's one burndown.
-
The usual approach to this is to divide pages near or at the top level of a space. For example, we often see spaces with two top-level pages, such that: * Home (unrestricted) * Internal (view restricted to only internal users) * Vendor 1 (view restricted to vendor 1, and internal users) * Vendor 2 (view restricted to…
-
Not sure what you mean by "document" In Confluence, your users need to be licenced in order to use it (although there are some options for "anonymous", it is very rare that you should allow anything other than read-only for unlicenced users, and certainly not create space). To create a space, * Your number of active users…
-
That does not tell me what you have done in the add-on to tell Jira how to link to it.
-
So what have you put into the add-on to link to it?
-
I'd guess that you are looking at projects that were not created as "next gen" - next gen projects are the only ones that have the roadmap function.
-
Yes, and deactivated users do not count towards your licence limit.
-
It depends on what you have written to provide the UI for the add-on. I can't tell you how to make something visible when you have not told me what you have created that needs to be made visible.
-
Possibly, but you need to try increasing the time-out as mentioned in the doc (you've tried the other stuff, but I just realised there's it's the one thing you have not spoken about)
-
Go to the issue. For a field to appear on a request, it has to be available in the issue.
-
Deleting users is bad practice. Disable the user instead.
-
No, I am talking about the panels that the screens are divided into.
-
So the reason field is on the request and hence will be on the issue behind the request. All you need to do is look at the issue.
-
If there is a dead link, you have something wrong with your network - it's blocking access to the pages in Jira.
-
You need to enable support for proper standard email protocols in the EWS server - look for SMTP and IMAP setup (Or POP, but try IMAP first)
-
Go to https://<your chosen name>.atlassian.net
-
I don't know. You have not told us what is creating the recurring tasks. Jira does not create issues itself. As you have recurring tasks being created, there is some person or process creating them. You need to look at whatever is creating them to answer your question.
-
I am afraid your question does not make much sense. Could you explain what you want your users to see?
-
Issues are not "next-gen" or anything else. An issue is an issue. You can set your boards (which draw in issues) to be scrum, kanban or next-gen.
-
You need to look at what is creating these tasks.
-
You did not say you were on Cloud, so I assumed server, which has three project types defined for business. The idea still stands though - pick a business project with the most complex workflow.
-
No, it reads config at startup and caches most of it.
-
Make sure the project is using a different "field configuration scheme" to the other projects, then edit the one it is using to make the fields optional.
-
Log in as an admin, then go to project -> notifications and click edit
-
Change the notification scheme for the project so that it only mails people on "issue assigned"