Comments
-
You can install them on the same machine. The only problem you will run into is performance - you need to make sure the machine has enough power (memory and cpu) to run both at the same time. The reason is that both systems are independent installations - if you run the installer for each, they will (by default) install…
-
Screens are determined by workflow and issue screen schemes, not by user. You're right in your solution though - you can set up transitions that duplicate, but have different screens and conditions. For example, have Open -> Closed (1), with Screen 1, and a condition of "only group X" Open -> Closed (2), with Screen 2, and…
-
You will need to get something like Script Runner, which can create "scripted listeners" - a listener will need to catch all the "issue commented" events, read the current status and append it to the last comment.
-
With scripting, yes. But that would make the comments polluted and long.
-
It's been a long time since Atlassian actively recommended moving off SQL server, and even then it was only in certain circumstances. It is not the first database that would be recommended if you had no preference at all, but the advice now is very much "use what you are most familiar with / best skilled up for". So, I…
-
NEVER amend a Jira database, it is not intended for you to even look at, let alone change it. Stop Jira, restore the backup you took before you ran the SQL and restart and re-index, that is the only way to undo the damage you have done. Although you might be able to get away with creating a new project and deleting the one…
-
In 5.2, they were using the excel download which translated "<no value>" into "unresolved". The CSV export does not translate, it just gives you what is really there.
-
Annual maintenance on Server is half the cost of the initial licence. If you do not renew the maintenance, then you lose access to Atlassian support and you will not be able to upgrade (to any version released after the end of your licence). But it will continue to work as before. (Note that applies to the Atlassian…
-
Which test management app are you using, and what version is it?
-
Which test management app are you using, and what version is it?
-
No, it's simply reporting what is there - "unresolved" is displayed by Jira when the field is *empty*. The CSV does not do any translation, it just gives you the actual data (nothing)
-
Same answer on comments, only champions and admins can remove them. For the space limit, you need to be a system admin with access to the global settings for attachments, it's not a space limit.
-
The pricing is public at https://www.atlassian.com/software/jira/pricing?tab=self-hosted and you can buy there too. You'll need to decide if you want to run it yourself or use Atlassian Cloud, on the number of users and what other tools you want.
-
Get your admins to create a Scrum or Kanban project for you, next-gen doesn't do these yet.
-
An admin can change the limit of files you can attach, but don't go too high, the system is not a file store and large files tend to fail. Community doesn't have answer removal at anything below an admin level. The old system had problems with people removing useful answers and destroying good conversations
-
They're not fields, it's all one field. So, no, you can't get a handle on the bits of the field.
-
There's a reason the flag is called "accepted". Also, there is no "solution" - if you want to rank a list, you have to use a rank.
-
First, define clearly the process you want to follow, then build a workflow based on that.
-
The permissions are only editable by administrators. What you should do is give the project a set of permissions that are based on roles. Then your project administrator can put people into the roles in their projects.
-
This sounds like it should be a cascading-select list custom field.
-
The message under Jira Software confirms what I suspected - you have not got a licence for it. Get an evaluation licence and add that to it.
-
The main error you are getting is because the installation is damaged. There are missing files, or the startup environment files have been damaged and are not setting the paths correctly. I don't think you can do much other than start again, with a clean installation
-
This Jira does not have Software added to it, or it's inactive. Check Admin -> manage applications to see if it is installed and licenced correctly.
-
You either haven't got Software installed, or it is not licenced. Go to Admin -> Manage applications to check the status.
-
You either give them bulk-edit or you do not. It's not a project permission, it is global.
-
I'm not sure, I've seen this before with one of the testing add-ons, but also an issue templating one and a project management one.
-
You're misunderstanding the build of the system. Jira Core provides issues, workflows, projects, users, a plugin framework and so-on. Jira Software is an application which runs on top of Core, giving you additional functionality. You can't run Software without Core underneath it. It sounds to me like you are thinking of…
-
There is no "standard procedure" for copying directories - it's not something you would do for any reason other than backup. If you want another Jira installation somewhere, the proper thing to do is to install a clean one, and import data from a backup. It sounds like the AWS server is set up correctly, with a dedicated…
-
Put the admins in a new group, add that group to the global permission for bulk edit.
-
The first three (starting with create) are being added by an App, if you remove that App, they will go away.