Comments
-
It's not just the gadgets and reports that are affected. The whole of Jira (Core and SD) rely on the resolution at many points, and it's not a case of changing filters because they're hard coded and there are chunks of core code that rely on it as well. Even if you don't want to use resolution, then your admins need to…
-
Ok, but what do you see in the UI? Where are the duplicates there? A sample of the CSV, with column headers, would be interesting to compare (drop summary or text fields if you want, we don't need to see them)
-
Shut down Jira, restart the database server, and then run the check SQL mentioned in the doc (the database restart should not really be needed, but I've seen it be necessary once, so I wanted to mention it)
-
Problem is, Jira physically can't create duplicates, the database is structured to prevent it, as well as the code. So we need to track down how they are being created, how they are identified and how they appear in your system
-
That does not fix the problem that if you fail to deal with resolution, the gadget returns inaccurate reports.
-
I don't know what you're reading now - you will need to explain to me what you mean by "oauth project"
-
It's global.
-
On the same LAN section in the same building, ideally in the same room and rack.
-
It supports it fully, but I can't explain it better than the docs. All I've ever done is followed them and it worked.
-
How are you generating these duplicates? What do they look like, and how do you get to them?
-
You'll need some code or automation to do this. I would reach for ScriptRunner to do it, I am sure the Cloud version can add "create sub-task issue" code, setting the dates as it creates. (and because I'm a bit biased - working for the vendor of it means I've got free access to experts in it)
-
You will need to find or write a listener that you can add to do this in Jira.
-
This is a setting buried in a properties file in the installation. The default setting is 2, meaning "2 buttons, then dump all further transitions into a drop-down". You can't change it on Cloud, as it the file is part of the installation. But, if you are sure you want to change it to 3, then raise it as a support request…
-
Confluence is a wiki (that works well alongside Jira), providing a place for people to write documents of any format collaboratively. Tech docs, knowledge bases, meeting notes, requirements, internal process docs - anything you want really. Jira listeners are things you do inside Jira. There is no "development mode" in…
-
Run and save filters that pull the issues from the projects you are interested in, and then have a look at using the filters in dashboard gadgets.
-
What have you done differently to the docs, and do you have any error messages?
-
In your original question, the error is that there is something in your setup that is trying to allocate nearly 8Gb RAM to the JVM. My guess is that your computer has 8Gb memory, so when it tries the allocation, it fails, as there's other bits of memory in use for things like the SDK and Operating System. By default, the…
-
To do things the way you describe, yes, and there's no copying because that's not the way Atlassian expect you to use this sort of thing. But I really think the design of your implementation is weak. For example, think of the reporting. "I want to find all cars made by audi" - in a well designed system, you could say…
-
My usual mistake is doing all the right things in the server.xml, but forgetting to uncomment the connector I have modified, so it carries on using the old one. Your connector looks right to me, so I'm guessing it's not being read by Tomcat, rather than it being wrong!
-
Are you sure the flag was applied to the database and has persisted?
-
You need to work through all those possible reasons. There's no way we can tell you which one it is, even if you had given us a log.
-
JQL is for finding issues, not users or logins. The only "login report" you can do is to check the user list and look at the "last logged in". Bear in mind that records the last time they were asked to log in. If they are using the "keep me logged in" flag, their "login date" will not be updated while they're still using.
-
Remove the two directories it was installed in - the "home" and the "install". Drop the database from the database server. Check for any scripts in /etc/init.d and delete the jira user that was created. If you're on Windows, check the created services.
-
No. You could hack the database to increase the counter, but all import methods then carry on from the highest number, so it won't use your "reserved" numbers.
-
No, you need to provide it. But the licence scheme does explicitly support it. Install the Jira server version you want to run as a test rig as normal. Go to your licence section on my.atlassian.com and find your production licence. Beneath it, there is a link to a "developer licence". This must not be used for production…
-
You need to move away from the mistaken idea that there are scrum or kanban issues. There are not. There are issues that your board selects for view. You can see the issues in both boards because your filters select them. If you want to remove "kanban issues" from the scrum board, you need to change the board filter so…
-
The quick filters don't support those yet. You will need to create a quick filter for each one individually
-
In both cases, your administrators would need to find or write code that would be run by Jira and push data over to those systems when you need it to do something, and on the other end, write stuff that would talk to Jira over REST when they need to.
-
You are correct, it might not be the credentials, it might be some other access control. Whatever it is though, it is a problem with either the credentials or the server setup. Or, possibly, if you are using the wrong driver for Jira (if you have not installed your own, then you have a compatible one, as part of the…
-
So you need mutually exclusive board filters for the boards. That is under Board Configuration on the main page.