Comments
-
What has your (unknown field called) "title" have to do with hiding the issue key?
-
Yes, ScriptRunner hangs a good chunk of code off that field, so you do need it. You should add a replacement field of that type, make it global, and re-index the whole system (background index will do, you don't need the locking one)
-
No, there's no way to "bypass" the limits. They're not really imposed by the software, they're more about the limitations of the services and hardware that cloud runs on. Your only option is to import spaces one by one, and if a space is too large, you will have to shrink it before exporting.
-
Those are the only options available on Cloud (unless you get Apps to add more). For info, the Excel option was removed a couple of years back, in favour of CSV, as everyone wanted CSV instead.
-
I think you are misunderstanding burn-down and what story points are for. The burn-down of a story should happen when it is done. You do not burn down until you can say to the end user that it is complete. Your burn down charts are "accurate" as long as you have set up the board correctly - all status that mean "done" are…
-
The estimates on a sub-task are of no use in scrum. In scrum, you say "We will do X points, covering these stories". You then deliver them, or you do not. There is no partial delivery (your customers do not care if you deliver 1 point or 99 when you promised them 100 - you either deliver what you said, or you do not) In…
-
Yes, you can create a new board, where "done" for the developers means "ready for implementation" for the clients and implementation managers.
-
Atlassian's policy is to provide the ability to take a download every two days. You could try asking if they will change that over at https://support.atlassian.com/contact but I think the policy is global.
-
By "account", do you mean a user account, or you have two separate Jira instances?
-
It's the same answer you found, but you can't make that change because you can't change the properties file you need to (although more recent answers will point at a slightly different file, as it has moved) Last time I asked, Atlassian support will change it if you raise a request with them at…
-
It's been a long long time since I write any code for access things over SOAP. I would still take the same general approach - write code that pokes the remote server, waits for a response and then parses the results to check for errors. If there's a failure or timeout, record it or fail gracefully (For example, if you're…
-
By "block", I guess you mean "stop them using the projects". To do that, either remove them from the groups and/or roles that grant them access (look in the permission scheme to see who has "browse" and other permissions), or change the permission scheme so that it does not grant them the rights any more.
-
I've seen this happen when the UPM is a buggy version, when the server is struggling (check the CPU and memory usage when trying to load one of the descriptions), when I've made a hash of a plugin descriptor in my code, and when the Jira server has not been able to reach itself over REST (i.e. I've messed up my https…
-
See https://confluence.atlassian.com/adminjiraserver072/supported-platforms-828787550.html "supported platforms" is the phrase now tattooed across my brain for "what does <atlassian thing> run on"
-
That probably changes it again. The plugin usage is probably going to be less use than you think because a lot of the functions in plugins in Server simply don't exist in Cloud. The plugins and even the plugin frameworks are totally different (barring the small handful Atlassian support in Cloud - Tempo for example).…
-
It's because you cannot know what any given plugin might do, and "user is using plugin X because we know they are doing Y" could easily be totally different from "user is using plugin X because we know they are doing Z". The way to work out who is using a plugin that just provides a report is totally different to the…
-
No, it's not. Macro usage shows you where macros have been used in Confluence. This conversation is about where plugins/add-ons/apps are used. Not macros. Macros can be provided by apps, but even when they are, macro usage is only one of the possible ways an app could be being used in Confluence. And if people don't use…
-
No, because of the reason above. Anything that could do that analysis in full would have to understand what several thousand different plugins do.
-
Yes, absolutely ok. Summary is a required field on all issues, so reusing it for "title" (which is usually a poor choice of words to describe the field anyway) is a very good idea. For the other system fields, the rule of using them is pretty simple - use them for data that is similar to or the same as what they're…
-
No, there's no undo, you have to go find the old data and put it back as a new update.
-
Sorry I couldn't really solve it, I think we're stuck with the templates only saying "hey, I'm a date" for full date/time sets.
-
Off the shelf, a Kanban board's "done" column works off a "release". If an issue has a fix version, then it will not appear on the board, because the board sees the version as the "release". You clear out the column by using the "release" at the top of the column, which sets the version to something when you use it. You…
-
That's another totally different problem. You are trying to upgrade a running Jira. The script tries to stop it, and fails for some reason. You need to shut down a Jira to upgrade it. You need to read the log file to find out why Jira has not shut down, and possibly forcibly kill it if necessary.
-
There is no lead tracking project type in Jira. (In fact the types are just Business, Software or Service Desk, and although these each have a few templates, none of the built-in templates are "lead tracking"). Your admins have configured that, or possibly added an App that adds it, but there's no off-the-shelf template…
-
It sounds like an admin has removed the admin groups from the global permissions, or removed you from the admin groups.
-
Not without hacking ScriptRunner.
-
That's not a project type that comes with Jira, so I assume it is a project you have configured yourself. I don't believe you are talking about "resolution" here, I think "won" and "lost" are status, indicating the current place the issue is in the workflow. They're not values you select for the resolution field. Your…
-
There's no error shown
-
Confluence doesn't have the functions to classify pages like Lithium does.
-
The first message you show us tells us that Jira is not running. You should check whether it is running, and read the logs to see what is wrong with it. Your second message is about Confluence, not Jira.