Comments
-
For all the projects the board might include?
-
This is where you need to talk to your Jira administrators. We're a community of end users who mostly have no access to your system (you might well be the only one here who does), we can't really help you. We might be able to help your admins when they're trying to fix this problem (I can see that your system has lost its…
-
What is the board filter? (Board -> General config, should tell you what it says)
-
A licence is just that, a key that enables functions in a system (In Jira's case, more users are enabled) An upgrade is a different task - you need to run a set of these as a project, to get yourself up to a supported version. (I'd go 5.0 to 5.latest, to 6.1 to 6.latest to 7.0 then whatever 7.x you want to end up with)
-
There is a set of options (add gadget, change layout and <...> for more) towards the top right of your dashboard. Assuming you are logged in as the owner of the dashboard.
-
That looks like a Core business board to me. So there's no configuration needed.
-
There's a bit of a disconnect between Jira Software (Boards) and the Core Jira (where you changed the workflow). The workflow in Jira doesn't care how it's been mapped in the boards, and it's actually a bit of a nightmare to even do the simple "warn people about specific boards when status is changed". Issues not appearing…
-
If a user can see the request, they have access to the attachments. You can control activity (edit, transition, etc) with permissions and workflow conditions.
-
You need to remap the status from the new workflow into the columns. Go to the board, then board config then columns.
-
Please see the original answer.
-
No. If a user can see the request, they have access to the attachments.
-
I'd do it the first way - with copying over to a new server, you'll get to do test runs while leaving "live" running. Then, if something goes wrong on the day of the real migration, you get to keep your old system as a really easy fall-back.
-
Admin -> General config will let you change it on Server. Bear in mind that the base url is only the internal Jira part, you will still need to update your DNS services to land on the new url. You can't change the base url on Cloud - the only option is currently to export everything, get a new Cloud and import the data.
-
Yes, a developer licence will work for all versions from 4.0 upwards.
-
There is a contradiction in your question - you say the space is not access restricted, but the message you are getting clearly says that it is. That's a little confusing, but the error message is the important bit. You'll need to talk to the space owners, your admins, or the owner of the parent page - these people will be…
-
As I said, you need to fix the certificate error. You can't create an application link unless the two systems are able to talk to each other. The certificate problem is currently blocking that.
-
Ah, right, then I don't think you're going to have a lot of luck. This is an Atlassian forum, and although we all have experience in non-Atlassian areas, it's pretty unlikely that a lot of us do. When it's a field that's not Atlassian or directly related, it's quite likely that the overwhelming majority of people here will…
-
A clean install won't contain any of your data - I assume you will want to do an export and import at this point. An upgrade is going to be easier. The data is the same as your export/import-on-clean, so that wouldn't get you around any "inherited issues". In later versions of Jira, the standard upgrade process will help…
-
There's no way to give you a fix for this, because we don't know what the problem is. The most likely answers are that you have not given the correct permissions to the directories involved, or that the directory is owned by the wrong user. Check that first. If that is not the problem, then the next test is to log in as…
-
Delete the existing one, then click create again. The certificate error is the problem though, you have set up an invalid certificate requirement on the Jira side, so you'll need to fix that before trying the application links again.
-
You need to create the link on both sides. The Confluence you are trying to link to does not have the link to your Jira, it's not been created, so the current link you are trying to create in Jira needs to be dropped and removed so you can try again to create a new one.
-
There's not a lot of point in "experimenting around it". Jira is unusable without it, so all you'll be doing is wasting your time.
-
You disable the system add-on that provides it by removing it from the installation. This has two problems: 1. It affects all projects 2. It removes all the project data, rendering Jira pretty much unusable (you won't be able to configure projects and your users are going to have to remember the direct urls to get to…
-
Converting to Cloud, yes, this is well-supported by Atlassian, with the caveat that your data must not be too large to fit into Cloud. Cloud currently only goes up to 2,000 users (active, not just people reading stuff) and 100Gb data, and although there are plans to increase the limits, if you are close to them now, you…
-
This is a standard Linux security system kicking in. Services cannot run on ports below 1024 unless they are run by root. Three approaches: * Run Jira as root. Except, do not do this. You absolutely do NOT want to run Jira as root, that's a much bigger pile of security problems than this blocking behaviour * Run Jira…
-
Yes, you will need to recreate a project suitable for the new stuff.
-
On the "missing password" problem - you were entering user credentials from the system you were restoring from right? The system import brings in the old user accounts, overwriting the ones you set during install/config of a bare system. There's not a lot we can do without knowing what the "missing object types" being…
-
Jira is already an issue tracker that stores a history of issue change, so "issue updated" is part of the data, not a parameter. Use a REST call to a query that includes "updated < (length of time ago, or specific date/time" However, I would question what your reasons are. Why are you "capturing data"? Jira already…
-
There's no way to track browsers being closed. Same way there's no way to track if a user is actually looking at a screen. However, closing a browser is NOT logging out. The user is not logged out just because they've not got a page open in the application.
-
I agree, but it's more a case that Microsoft resist doing things in a way that the large majority of other systems are doing things. More and more, we're seeing services making the assumption that "when I connect to X, it's there, and I don't need to round-robin/check-others etc, because X will handle redundancy for me"…