Comments
-
I can pick up the first question, I know what it means. The answer is "no". You have to use an atlassian.net url. You could use a domain of your choice and run a simple "redirect", or even a proxy on it over to the <something>.atlassian.net, but Atlaasian applications have a single base url which your users need to use.…
-
11th to 14th if I my second-hand information is correct
-
No. You need code. If nothing else, your code is going to have to implement a rule to decide which date to roll up, as an Epic can have many stories.
-
Correct, Jira tries to keep the display as uncluttered as possible, and one way to help with that is to not display empty fields. Your product owner is stuck - she's going to have to go into edit (or a transition) to fill in the field. Or you could make it mandatory, so it is always filled in.
-
You can't format the name of a field, they are rendered by Jira using a standard set of html/css.
-
I would strongly recommend forgetting Jenkins here. Bamboo integrates with Jira off-the-shelf and is a far better solution in general. With Jenkins, you're going to spend hours configuring plugins and config to get the basics working, whereas Bamboo will integrate better, provides more CI/CD functionality, and only needs…
-
SR should install and configure the field automatically. If it has not, it might be worth having a word with Adaptavist Support (Yes, I work there, no I don't do SR support)
-
As well as WebDav, you can use the REST API. Do not just try to dump files on it, if you don't go through the API, Confluence will not create the data it needs to be aware of the filess.
-
Create a filter for "project in ( )" and save it. Create a new board, using the option "create from filter". You now have one backlog for many projects. You can then use "configure board" and "quick filters" on that board.
-
Also, what are the other fields on the screen?
-
Sometimes, yes. Often, people will do it differently.
-
I'm afraid the layout of the fields simply doesn't support it. You'd need to hack the core code (or use some horrible javascript that wouldn't work half the time)
-
I am sorry, but your first sentence makes no sense to me. I am guessing that you might be talking about the function that Service Desk tries to suggest Confluence articles to you when you raise a new request? Is that right? If so, then could you explain the problem?
-
Start with a look at https://confluence.atlassian.com/bitbucketserver/migrating-bitbucket-server-to-another-server-776640406.html and https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-applications-861253088.html
-
It's too deeply buried to be worth un-picking, and there are far too many big clients it would break things for (for exactly the reasons Romer mentions, as well as others). It's not going to change.
-
See https://confluence.atlassian.com/doc/database-setup-for-mysql-128747.html
-
From the many questions we've seen about cPanel, it does seem like it's too primitive or inflexible to give you the ability to install Atlassian products properly. If you don't have cPanel, the process is simple at its heart: create an empty database, run the installer and tell it where to install and find its empty…
-
Once the first one is running, further requests are ignored until the first one has ended. If you kick off a full re-index while a background one is running, then the background one is terminated. And you can't (easily or quickly) start a background one while a full one is running.
-
You need to be a bit more clear on answering Gaston's questions. How are you marking done and closed? Do you have specific custom fields for tracking? What action determings the assigning? etc.
-
Not really. An admin has to do admin, which covers both spaces and users/groups.
-
Boards do not belong to projects. There is nothing to stop you having one or many Scrum boards and Kanban boards all looking at the same project (or set of projects) The board you see in your picture is simply the last related one you chose to look at - try clicking the arrow next to the name of the board to swap to…
-
Exporting to xml is intended to give you a spreadsheet that represents your issues so you can manipulate it into reports or transfer it around. Importing has nothing to do with that, it's about importing records line by line. The export/import are not designed for Jira to Jira transfer, they're independent functions.
-
"It doesn't work" does not tell us anything. It could be a technical fault on the certificate, or on the server, or an angry penguin grabbed the certificate, ran off, and is now taunting you from the top of a filing cabinet. Flippancy aside, the KB articles I suspect you have found are generally going to be right, but you…
-
Installing it as per instructions usually fixes this issue (although it includes reading the "fine print" - check every detail!) I would guess that is what Vamshi did.
-
You're not hitting the limit of what Jira can technically hold (you're not even close), but you are running into the problem that it does not have enough resources to handle them, and, of course, you're way past the number of links that is even vaguely useful.
-
What url is displayed when you hover over the 78?
-
You only have "project administrator" rights, not system or Jira admin.
-
I'm not getting that problem at all (and given there were 80 people in the training doing the same thing today, I don't think I'm alone). What does your log file say when it's failing?
-
The script you have on your post-function is clearly not what you say it is - for a start, it's failing on line 6, so there must be more script than just your 'log.info' bit.
-
You can't. Confluence 6 dropped all support for 32 bit installations. In theory, you could try to install it and then unpick all the contents and place them into a 32 bit Tomcat installation, but I seem to remember that won't work as even they have been compiled for 64 bits. I suspect your only chance might be to download…