Comments
-
You are completely right. +1 as a comment is a complete waste of time, it's noise for watchers and makes you look daft because of that. In many cases, it's spam - bots or sock-puppet accounts saying it becuase it makes the account look a bit more real In systems that do not have voting, it might be of some use, IF the…
-
Frustratingly, no, we have to add validators, triggers, conditions and post-functions manually, one at a time. (Other than the "mandatory field" and "user has transition permission" ones, done automatically or by the field configuration) There is no built-in function for "non valid", you need something like Scriptrunner to…
-
You will need to install one of the scripting or automation apps first, then have a look at their getting started guides and code libraries.
-
You will need to write your own authentication system for each of the applications. Although this looks old and I suspect some of it is out of date, the principles remain broadly the same. See https://confluence.atlassian.com/kb/single-sign-on-integration-with-the-atlassian-stack-794495126.html After skimming that to…
-
If they are inconsistent, then read the upgrade and application logs to see what ight be going on. There should be some errors in there telling you the upgrade could not update something.
-
It's not the built-in query used by the gadget - it can't be because it doesn't work. Please, correct it and see what it returns in the issue navigator - we need the list of issues you are reporting on to see why the gadget might be wrong.
-
Yes, adding a custom field to the issues, but not actually putting anything in it will give you an empty display. I would throw that field away and replace it with a "scripted field" - Scriptrunner (I name this first because I work with the authors, and have used it for a lot longer than joining them, so I am most familiar…
-
How many issues does this return, and how many are in the project overall? Does chopping bits out of the query make it faster (I know this makes it less useful, but we're looking for a point of slowness, not a working query). For example, how do * Project = CQDS and issuetype = bug * Project = CQDS and issuetype = bug AND…
-
Confluence tries to use a friendly human url for pages where it can, by using the page title (replacing " " with "+" to make the url valid). If you use any special characters that are not valid in urls (other than " "), then it can't generate a valid human url and falls back on the page ID instead. I try to avoid using…
-
I don't use powershell, I can't tell you what is wrong with the code, other than it is not presenting the right authorisation data to Jira. Check what your script is doing against https://developer.atlassian.com/cloud/jira/platform/jira-rest-api-basic-authentication/
-
That suggests your upgrade did not happen, or if it did, it failed to update several files. Check the help -> about, and system information pages - do they also report 6.6.2? If they are consistent, then it's pretty clear that your upgrade did not happen (it might have installed in a different location for example, leaving…
-
Look at the screenshot you gave, note that your query is wrong and the error message in red is telling you what the problem is. Correct that first, then we can look at everything else.
-
You can't change field formats in the UI, the only way to do it is by amending the database. You will need to be very careful if you do this, as database updates often completely wreck a Jira as most people don't understand the database well enough to do it properly. In this case, the process would be: * Stop Jira * Backup…
-
You've used the wrong password too many times, or you have been removed. You will need to use the password reset options and possibly contact your administrators.
-
What is a "check in" of a person?
-
Confluence is not a system that presents anything as a directory, it is a server providing a service. You don't "connect it as a network drive", you use a browser to access it. It does provide a WEBDav interface as well, but that also is not quite a "network drive", and if you do use it, you need to get the settings right.…
-
Not directly from the UI, and you can't do it easily directly on the server. They are kept in one directory (per issue), but not with the names you see on-screen. To get a zip of all attachments, you should scrape the issue with REST and build the archive in a script.
-
I can't. The explanation is answering a question about field data during a move, not for a specific field, but for any field you might have on an issue.
-
With the small amount of memory available on a Pi, it's going to struggle to start and take a long time to do it. I would not expect it to start listening for several minutes - did you give it plenty of time to get started? What does the bottom of the log file say about whether it is running or not?
-
Your call to the REST API is incorrect, it's asking Jira to do something the API does not do - check the calls you are making are supported and valid, and that the account you are using has permission to perform the requested action.
-
There's a bit of history in this - Jira has always done estimates in the way you say, but Jira Software adds a burn-down chart, which should not use the cumulative totals on sub-tasks because you're supposed to burn-down when the item is complete, not partially. This leaves s in the odd position that sub-tasks can have…
-
There is no "matching" or "scripting" here, all you have done is configured a field to appear where you don't want it to. For a field to appear on an issue, the field * Must have a context (see the list of custom fields) * Must be on the "screen" in use. Issues all have three or more screens - create, edit, and view, and…
-
I do not quite understand what you are doing here. I do understand that you have two different workflows, but you don't explain how you are using them or what you want your code to do, because you have not told us what you are doing with the issues involved. At a guess, I think what you might have is: * Issue A, of type…
-
You can "pull" the data via the REST API - see https://developer.atlassian.com/server/jira/platform/rest-apis/
-
The error message tells you what the problem is - Jira can't reach the database. You'll need to fix that and restart Jira.
-
Versions management is part of the project admin role, and is not granular like that. If you are a project admin, you can add, edit or delete versions.
-
You don't. Burndown measures your delivery of the items you said you would do at the beginning of the sprint. Sub-tasks are part of those items, not deliverable items in themselves. Imagine you said "in this sprint, we will build one house". Sub-tasks are things that are part of that, so things like walls, roof, plumbing,…
-
They do increase the memory demands of Confluence, but those two are quite small compared with others. I would not worry about them.
-
It is a false positive. Sourcetree is not malicious.
-
The page you've pointed to is the full list of supported arguments that can be used. There are some others, but they are developmental or "dark" so you can't rely on them being there in any particular version, and they may be harmful, so you should not use them.