Comments
-
If by "online" (as all Jira systems are "online" or not running at all), you mean "Cloud", no. You can only export to CSV, which spreadsheets can all read.
-
The project settings allow you to default the assignee to unassigned or the project lead, but it is more powerful than that - see https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html
-
There is no way to do this. The sequence number is a number, not a string, you can't pad it with 0s. Even if you hacked the core of Jira to persuade it to pad it with leading 0s, the whole thing treats the sequence as a number, and you would need to add code to convert back and forth between number and string in a huge…
-
Whatever you define it to be. It's not a standard Jira field, so it's something your admins have added to support one of your processes. My guess would be QE is an abbreviation including "quality" somewhere, but it could also easily be related to quants if you're in a financial organisation.
-
There are a couple of ways to track "progress", but it very much depends on your processes and what you really think it is. Your idea about start and end date is quite good, as it's measuring elapsed time The most simple measure is the number of open and "done" stories in the Epic, but this takes no account of size Story…
-
Ah, yes, the new view is also going this way. You'll need to configure each one separately.
-
Are you moving a top-level issue and the sub-tasks are going with it? What automations do you have in place?
-
Next-gen project issue layouts are independent of each other, not shared, so you'll have to configure each one separately.
-
There's no way to do this. Workflows are not stored in the database in a way that would facilitate this (and reading the database is always the worst possible way to find anything in Jira anyway). I'm afraid your best option is to read each workflow.
-
No, if something can see the issue, it can see all of it. This suggests that Boomi is not yet able to cope with Jira custom fields.
-
As a follow up to this, it really sounds like something is corrupting the index. It is likely that this is going to continue to damage the index, leading to more and more need to re-index the project and destroy your people's faith in the system and hence usage. You should identify what is doing this damage and fix it as a…
-
Manually copy them probably. Unless your test-management app you've added to Jira has some form of export that is aimed at Mantis, I doubt there's anything much better than copy and paste available.
-
All of them. Atlassian do not make "unstable" releases available (they do release "early access", which are arguably "unstable", but they're flagged as such, and released separately)
-
No, absolutely not. You must perform a proper upgrade from 3.5 to 4.x as per documentation. "just copying" will not work.
-
I would think about using six separate projects, as it seems each team has separate (although linked) products. But if you do it in one project, I would use components to separate the six team activities. For automatic moves, you'll need an automation or scripting app to build the rules you need. It sounds like they may be…
-
Start at https://developer.atlassian.com/server/confluence/confluence-server-rest-api/
-
You need to be an administrator in order to get into the general configuration.
-
No, there's no way to do this easily. You'd have to turn off the code that makes the "pretty" urls. I tend to use the short links (in the page properties) which are also invariant.
-
There's no way to do this without writing a new gadget that can reach out into the other system and run queries on it, then display it locally.
-
In theory, you can change it to such a scheme, but it will break a surprising things in interesting ways. I've had to "repair" this several times in the past, just to get through upgrades or make apps work. You should stick with project keys that at the very least start with a letter, and then 1-9 alphanumerics. I would…
-
This area is not filters, it is a set of links to various parts of the project. There's no way to add filters to it, as it's not for filters - they go under issues and filters in that list (and aren't customisable there either) If you find or write apps, you'll find many add themselves into this area when they are adding…
-
Projects don't have dashboards yet (there's an open request for them). I've not found an app that provides them either.
-
Ok, that looks like a healthy startup. We'll need to see the atlassian-jira.log
-
Jira is not aware of sub-groups, it just sees one single list of users in a group. I suspect it will fail for members of sub-groups. But, yes, it should work fine for data centre.
-
Start with a look at the log file, that should tell you why it is not running. I'm afraid there is no "jira.log", that seems like a blind guess to me. The logs you need to look at are <jira home directory>/logs/atlassian-jira.log <jira installation directory>/log/catalina.out The first will tell you if the service has…
-
I think there are some minor problems with your /s in the settings. First, In the proxy settings file for apache, you should make the ending of urls consistent in the proxy pair. So ProxyPass /jira http://localhost:8080/jira/ should be ProxyPass /jira/ http://localhost:8080/jira/ or ProxyPass /jira…
-
You'll need to adjust your environment so that it points to the right version of Java, the one built into the Jira installation. Set the JAVA_HOME variable to the root of the jre in the Jira installation, and make sure $JAVA_HOME/bin is in the path before the system installed Java, then run the batch file again.
-
That's a very old unsupported version of Jira, and Atlassian will not be editing the documentation for it (or allowing you to)
-
You'll need an app that can read your LDAP source for the extra details and display them. There's a couple in the marketplace I believe
-
You are right - it remains vulnerable.