Comments
-
Yes, you can buy as many Cloud systems as you need.
-
This sounds like you have had your Jira Software access removed, (but not your Jira Core). Do you have a "boards" item in your menu? Can you check your access rights?
-
Strange error message, that looks like a bug to me. But yes, the limit is 50
-
Heh, I did not know what the <random hardware> was. Don't even bother trying to run Jira on a machine with less than 1.5Gb of RAM, it will not be usable.
-
GC Allocation failure means that there is something going wrong in the computer's memory. Sometimes, this means you have not given the Java virtual machine enough memory to work with, but more often it means you have added something to Jira that is not well-written and it is misbehaving. In some cases, it can be as simple…
-
Use the "move issue" option. The issue type is not a field, it's structural and usually cannot be simply "edited"
-
>I used CREATE Database command to create a NEW database. Good, that is exactly what you need to do >There are always some default tables created with CREATE command. No. There is not. If you create a new database in PostGres, you get no tables in it until you create them. When I look at the databases I have here, the…
-
Great, that tells us the account should be able to do what is needed, but "cannot use" means what it says. Either the network is not delivering the right data, or that user has no rights to view your confluence.
-
This is not how Jira Software works. The pre-population of the sprint name is being done by something your admins have set up. You should ask them what they have configured and get them to change it to something more useful to you.
-
You need to log into the old account and change the email address on that, then you will be able to change the new account's address to it.
-
It's not about configuration. It's about where data is captured. The "work description" is a field intended to capture information about the work that is being logged. The field is part of a data item that is about work that is logged on the issue. It is not directly a part of the issue. You can't have a "work description"…
-
What do you mean by "its summary can link and display "ABC-1""?
-
Your settings look good to me, but there are a lot of problems that could lead to the errors you are seeing. Could you have a look at the application log to see what they are reporting the problem as? <jira home>/logs/atlassian-jira.log is the first place to look.
-
The only way that can happen in Jira is when the workflow you are looking at is different to the one associated with this project and issue type. Or there is something horribly wrong! Next steps here are: * In your last screenshot, there is a "(view workflow)" option. Can you click that and check that you come up with the…
-
My best guess is that you either did not publish the workflow, or you have not put it into a workflow scheme that is associated with your project.
-
Not natively, you'll need a scripting or automation app to set up something that sums up the estimates.
-
Yes, this is a confusing one - it's not that they use the same issues, it's that they could. A sprint will appear on a board if it could affect issues that the board selects.
-
If it can run the right version of Java and provide a network route to Jira, then yes.
-
Yes, separate boards and projects, but there is only one sprint. It's appearing in both boards because it could draw in items that are selected by both boards. What you probably want to do is look carefully at the board filters, and modify them so the boards can not display the same issues. You'll then find the sprint only…
-
Sprints do not belong to projects, they are global objects. Boards are not containers, they are views. What you're doing is looking at one view, renaming a single object and then looking at it with another view. Of course the name is going to change in view 2, you changed it.
-
You will want to create a user to run the service as, ideally, and you'll probably need root access to set up firewalls and networking properly.
-
No, it's not in 7.3. You will need to upgrade.
-
I am not sure I understand the questions. To install Jira on a server, you need to run the installation program/script that you download. You will often need to think about the networking to ensure the ports are open so people can reach it over the network. I don't know what you mean by "special means needed that a…
-
Yes, it probably is downtime - if Jira isn't running, it can't collect the data for the graphs.
-
On Jira 7.12, you can grant users (project admins probably), extended permissions, which allows them to make some changes to workflows and fields.
-
Give your developers "browse" in the project permissions, and no other rights. They will then be able to see the backlog when you share the board with them, but not change anything in the board.
-
I'm afraid not, it's returning all the status detail you might need, including the status category. There's no way to drop bits of the status response.
-
* Yes * No (Best case - they will just be recreated. Worst case, your installation will fail) * All of them * Depends on how much data you want to store in Confluence The usual culprits for large disk usage, and places you might want to do some cleaning in are * Attachments - you don't want to delete these directly, do it…
-
Use an "or" project = ISP AND resolution = Unresolved AND (environment ~ "\"production\"" or environment ~ "\"testing\"")
-
No, the button just releases everything. You can do it manually though - run a filter for the issues you want to release, (e.g. project = x and status = done and updated < -6w) and use bulk-edit to set a fix-version on them.