Comments
-
No. Workflow is a process the issue is supposed to follow, not a process a human can arbitrarily do differently. If you need a different route through the process because you are "special", then you need to build it into the workflow (extra transitions, protected by conditions that say "only special people can use this…
-
Unless patches and upgrades are specifically called out as being an exception, they are irrelevant. It says 2016 and doesn't mention patches, so you can rely on them being supported.
-
You would have to be using a system that pulls your "DG" into Confluence as though it were a real user with an email address. A dummy account with the email of the list is about the only way to do this (and I would strongly recommend that you don't, as spamming 200 people who may not care with no way to unsubscribe…
-
We're end-users of Atlassian software, we know a lot less about your system than you do. If your admins have not been good enough to provide a method of finding them (like the "contact admins" option usually in the footer), then you'll have to ask other users. Often, I would start with the person who gave you the account.
-
The answer that you would have found on all the other postings is still true. Your options are * Separate projects * Ugly kludges that annoy users by stopping them creating after they've entered data so they lose it all * Add-ons such as ScriptRunner that can amend it dynamically
-
I am sorry, but you are in the wrong place. We are end-users of Atlassian software, not your administrators. You need to talk to your (SSO/user?) admins, and we can't know who they are.
-
Start at https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html and choose the version of Jira you are looking at from the drop-down near the top right!
-
This happens a lot because people do not think through ranking properly. A human can take a list of things and put them in order and handle it intuitively, but you need to have rules about what that ordering is, and you have to agree them with other people and explain them to computers otherwise you can't understand it.…
-
You don't do this with a script - check the general settings for the number formatting (and yes, that is a global setting for all fields)
-
Jira only goes up to version 7.something, and Confluence 6.something. Could you give us the actual version you are on now? (Also, Jira doesn't have a page tree, so I assume this is just for Confluence)
-
From this, we can't be sure what documentation you are looking at, or what your system is. Cloud and Server/DC systems have very different UIs, but also separate documentation. So, first, have a look at whether you're on Server or Cloud (generally, if your menus are across the top of a screen, it's Server/DC and if they're…
-
You will need to ask your administrators to add you to a group that has "create space" permission.
-
Yes, that's consistent with something going wrong internally and being cleared out by a restart. You'll need to work your way through the doc I pointed to (and follow the links)
-
Ok, I think you've hit one of the things in https://confluence.atlassian.com/jirakb/clientabortexception-java-io-ioexception-broken-pipe-225122378.html
-
Go to the field configuration for the project and issue type Task and change the "mandatory" flag on this "name" field to optional. It will not affect existing data - the flag is only checked when creating or updating issues.
-
You will need to read your application logs to find out why it starts to struggle and/or stops. Check <jira home>/logs/atlassian-jira.log and then <jira installation>/logs/catalina.out - those two will tell you of crashes. If it is slowing down and then stopping eventually, then it's more likely to be the first log, and…
-
Um, it does. The problem in the question is that the poster is trying to break it - they've asked to ignore one half of the data pair, which, as you say, means you can't tell Melbourne from Melbourne.
-
It's a better approach than multiple assignees - in the real world, that causes problems. I've never seen anywhere that allows many assignees that has not had massive problems with "I thought someone else was doing it"
-
Messing with the database is not something support will do. For this request though, you could import 999 issues from CSV and then delete them, leaving the counter starting at 1,000.
-
See https://developer.atlassian.com/server/jira/platform/rest-apis/
-
The installer upgrades existing data as well as the installation.
-
That is what the "perpetual" sections of the doc says, yes.
-
Think of "Jira Core" as a "platform" instead of a simple application. Jira Software (and Service Desk, and probably some others in the future) run on that platform. Any given version of an application will only run on a range of Core versions, and what this message is telling you is that the latest available Jira Software…
-
Yes, the GC error is probably the culprit, as Jira will run slow before doing it and then die as it happens. The important log here is the atlassian-jira.log, but a GC error is serious, it means there is something wrong with the memory settings, or you don't have the resources or run the system, or there is a memory leak,…
-
It is a flag to tell Jira when you consider the issue to be done. It's placed there when you configure the workflow/board for the project.
-
Do you mean An issue's current status? If so, then you will need to use a transition from "abandoned" to "implementing" (also represented by you dragging the issue card between columns if you're looking at a board rather than the plain issue view) or The name of the status? If this, then log in as an admin and go to Admin…
-
Right, so you said the field appears "on create", but now you've said it is on "log work". Assuming you were wrong the first time and it is on "log work", then this is the work log description which will appear with the author and time logged in the work log tab on the issue for which they logged it.
-
Far more than you'll ever generate and still find useful! There are projects out there with hundreds of thousands.
-
Admin rights and project rights are (rightly and sensibly) totally separate things. Deleting a project is an admin thing, deleting an issue from a project is a project permission . Of course, an admin can always change a project permission to give themselves project rights, but I would caution against it - every posting…
-
Could you try the developer tools in your browser? This can often show that custom javascript is the problem (it will "leak" in the source of the page). It's another reason we recommend never using js Jira hacks.