Comments
-
It's definitely an installer - you run it, you get a running installed usable version of the software. Sure, it's rarely got everything most of us want it to do, but I wouldn't expect an installer to try to cope with the 5,000ish variations I've installed over the years, especially as the overwhelming majority of that…
-
We can't tell you anything, you need to read your application log file (probably atlassian-jira.log in <jira-home>/logs) to find out what the actual error was. The log referral number is a reference for your admins and Atlassian to uniquely identify the log the real error was written to.
-
The log referral number is a reference for your admins and Atlassian to uniquely identify the log the real error was written to. We can't tell you anything, you need to read your application log file (probably atlassian-jira.log in <jira-home>/logs) to find out what the actual error was.
-
The log referral number is a reference for your admins and Atlassian to uniquely identify the log the real error was written to. We can't tell you anything, you need to read your application log file (atlassian-jira.log in <jira-home>/logs) to find out what the actual error was.
-
Start at https://www.atlassian.com/licensing/purchase-licensing to see how it works But for 10 on the three main applications, it's $30 - $10 per application.
-
Epic links are a bit funny - they're not quite links, but logically, they are. If you've got a script for "create issue X from Epic-123 and link X back to Epic-123", you're almost there. But replace the "link X back to Y" with "update custom field 'epic link' with the 'epic name' on Epic-123"
-
That all depends on what your admins created the status for and how it is used in your workflows! My guess is that your processes have some form of refinement or authorisation in them. As someone who wants something done, I'd create an issue and would be "open". After someone on the development side (product owner maybe,…
-
There are many "integrations" you could be doing, and you keep just telling us the same thing. I would not be asking what this integration is if your words told me. Please, please, explain what this "integration" is? Name? Link? Something you did yourself? Something in Sharepoint? What is it? "It's not going through" is…
-
The workflow behind this project is not setting a resolution on issues as they move into "done". Jira Software considers the last column on the board to be "done", but the core of Jira (where the created vs resolved report comes from) looks at the resolution. If it's empty, the issue is open, if it's got any value, the…
-
This would make your Epics represent things we would normally see as projects in Jira. This is also not at all a bad idea. Epic = giant thing too big to tackle alone. Project = big pile of things that add up to provide something. They're not that far apart. I'd still try to break up your work along project lines, and then…
-
The classic projects have shared configuration that would allow someone who can administrate them completely trash everyone else's projects. So the creation and configuration of them has to be done by admins (who, in theory, know how not to trash other people's projects). Next-gen projects do not support sub-tasks. Yet.…
-
That's a business decision. The question to ask each project owner is if they need the data you find there. If they do not, then you can kill the fields.
-
You'll need to use one of the automation or scripting apps (you could write this stuff yourself as a new app, but that's inflexible and hard to maintain). These enable you to write bespoke processes or code inside the application, so you can write things that trap "story updated, add up new numbers on Epic" or "Epic…
-
First, you are making a couple of incorrect assumptions about the relationships between issues. * Whilst some issues can group together others, or contain subtasks, they do not affect the data on each other directly. Put an estimate on an Epic is fine, but it won't affect the stories the Epic might contain. * You also are…
-
"Integration" is too vague a word for us to help you with, beyond saying "use the REST API". Importing logs and test cases should be simple though - with REST, either get your test tool to push new pages or attachments into Confluence as it creates them.
-
You will need some sort of automation to attach a file every time, but I would recommend that you do not - you will end up with thousands of issues containing copies of a file that most people probably don't need or care about. I'd recommend using a simple link to the single standard document you want them to have access…
-
No. See https://confluence.atlassian.com/display/JIRA041/Supported+Platforms You really do need to upgrade to at least 6 to be secure though.
-
* Yes * Run the installer and answer the questions * They will be able to help you if you have a current licence and you raise support requests with them if something goes wrong For 6.4 to 7.11, you can just run the standard upgrade, but make sure you work through…
-
That's not quite right. A site administrator is someone who can maintain your entire Cloud set of systems. A project administrator is someone who can administrate your project, but they are often not a project manager, so the title is wrong. Your project admins do not need to be site admins to maintain users either, if you…
-
You told us you are having problems with a Jira/Sharepoint integration, but you have not yet told us what this "integration" is or what the problems are. "Integration" is always possible, but you need to define what it is before we can begin to help you. It is a "suitcase" word - it tells us you have something, but not…
-
If they do not contain data you might want to keep, then yes, absolutely feel free to kill the fields off. I would check by Rename all of those fields slightly, changing them to something like External issue id 1, 2, 3, etc, so you can tell the difference Run a search for "external issue id 1 is not empty", then for 2,…
-
I need you to tell us what integration you are trying to do. Repeating the same information does not explain what you are trying to do or how.
-
That's not what your error messages say. You appear to have Jira Service Desk installed with an invalid licence. If you don't want to be using JSD, that's fine, but you should reduce the numbers of people flagged to be allowed to use it down within your licence limit (which may well be zero if you have no licence) or…
-
It's a problem with the way versions are ordered and what we humans would use. Versions are not ordered by their name, there's an order in the database that gets used. It's explained a lot better than I can at https://jira.atlassian.com/browse/JRASERVER-22995 It's rather a frustrating one, because I'd like to see the order…
-
We need to know what the process is consuming and what it is capped as. When you run ps -ef and look for the Jira entry, you should find it running with a list of parameters. The most important one is knowing what the heap size is - the -Xmx#### parameter, although it would be good to see the others starting -X as well.
-
Thanks for adding some of the errors. Unfortunately, you have several which could be compounding and hiding others. There are two steps I would take here. First, get a valid licence or reduce your user levels to one that fit. The licence will not be causing a problem itself, but it is going to make it harder to do any work…
-
It's either secured from you, or it's been deleted. You can get issues back from backups, but it's a bit of a nightmare (which is why you'll find one of the most popular phrases in the community is "do not allow delete issue"). You'll need to restore the backup to a temporary development system, read the issues out and…
-
There is no way to do this as described - the project key is an integral part of the issue key, and the whole of Jira and its applcations and apps work on the project key being the first part of the issue key. The closest you will get is to create projects down component lines - so a project for Web, and other one for…
-
There's nothing attached here, we can't see your errors at all.
-
Does Redhat 7 run the version of Java you need to support Jira 4.1.1? If it does, then yes, they are compatible. But I would not use Jira 4, it has know security flaws and you really should upgrade as soon as possible.