Comments
-
Scroll down, it goes back to version 4.1
-
What exactly are you doing when you say "delete an issue from a backlog"?
-
The workflow editor will let you add a transition back to the same status if you want - you can stick a resolution screen on there, or even just a "set issue value" post-function so you don't have to choose when you use bulk edit.
-
Create a sub-task for each version. Jira can be set to close the parent when all subtasks are resolved, it will list them, with status, in the subtask section, and you can keep it really minimal with just status and a single version field and an open/closed workflow. Heck, if you want to automate, you could write a script…
-
I'm afraid that tells me nothing about your firewall, if that's what you're trying to show me. Plus it could be a firewall in the network, not the server.
-
Jira doesn't have templates, they're not a lot of use for issue tracking.
-
The context is a red-herring if you're getting "connection refused". You should get a blank screen if Confluence is running. Connection refused means the firewall or proxy is refusing to talk to you. If you have no proxy, it's your firewall settings.
-
It wouldn't be a burndown chart (or particularly useful) if you did that.
-
There's a link to the archives on the "download jira" page, but you now have to click through a few pages before you get to the useful one - https://www.atlassian.com/software/jira/download-archives Installing and upgrading them is covered in the docs, please start with them as they will take you through most, if not all…
-
Ok, you'll need to talk to your system admins - who looks after the server?
-
Are you on Cloud? You don't get access to the logs on Cloud. If you are on server, you may get a faster answer by looking at the logs and giving us the errors here (a support zip goes to Atlassian support, and it is sometimes faster to get help here)
-
Your site has enabled "anonymous access", which lets unknown users see your spaces. I'm not sure if you can turn it off globally on Cloud (check the "global permissions"), but you can certainly remove it from any spaces - check each space permissions for the anonymous access tick box.
-
Yes, I'm afraid you will need to re-do the key installation into a jks store. I tend to keep the key stores outside the Jira installation, in the jira user's home directory, so that you only lose the pointers in the setenv file on upgrade.
-
:-) Yes, injecting javascript to Jira is painful. It's unsupportable, often flaky and breaks on upgrades, or even addition or removal of add-ons. I'd not say "dangerous" really, as it's hard to damage your data (but easy to make a mess of it or break the way the screens handle), but you will find good Jira admins removing…
-
No, the description is a single field containing text with some simple formatting options. Tabs are definitely not simple formatting. If you used several fields, you could create tabs and scatter the fields through them.
-
Ah, text fields are not multiple value, so it has to treat it as an edit. I would take a different route - use a numeric field and a "increment numeric field" post-function. (Although I don't know if you have an add-on that provides one)
-
Ok, permissions are fine. I assume this is a Cloud installation? If so, then Atlassian have removed the options from that menu. I couldn't tell you why, it seems like a bad idea to remove it to me.
-
For the footer, https://confluence.atlassian.com/jira061/jira-administrators-faq/usage-faq/modifying-the-jira-footer still generally applies. Be sure NOT to remove the "powered by Atlassian Jira" section.
-
Ok, that's a good test. But can you check the conditions anyway, they don't have to be user based, it could be "has no open linked stories" or something. If there are no conditions like that, then it is likely to be a broken database entry, but I've never seen the integrity check fail to find one of those (Time out before…
-
I'm afraid not. The "move" function has nowhere to hook custom field checks into it - it only looks at the field configuration for the target issue type, and provides no insertion point for any code.
-
That's where I'd go if I were creating users in Confluence server. But are you still looking at Jira? And is it Server or Cloud?
-
You don't appear to have a confluence-admins group.
-
A site adminstrator looks after the Cloud site as a whole. They usually get included as Confluence, Jira, and Bitbucket admins as well, as the role is often "look after the atlassian stack we've got", but you could in theory remove that, so they only have access to maintain users of the site (of course, with that access,…
-
That's a Jira admin menu, you've tagged the question with Confluence. General config doesn't appear in a Jira menu (it's in the system area)
-
That log seems to show that you're trying to start it when it's already running.
-
Yup, that's one reason for putting in a vault with others. Just need to make sure your DBA is not a Jira admin and can't see the connection details for the jira database user.
-
I've seen it done with an add-on, but sadly it was proprietary and internal. These guys had build servers that dumped built copies of their add-ons into Atrifactory and then they wrote an add-on for Jira that could scan that for new versions of installed add-ons and list all the add-ons in Artifactory that were not…
-
It will work fine, as long as you, um, don't bother to use the vault functions. The Jira user in the database needs full, unrestricted access to everything in the Jira database. No other user needs any access. You don't need Vault to do that. But if you're asking because you just want to have Jira's database alongside…
-
That sounds like a broken usage to me. Why are you including deployment in your sprints? That's something that should be handled completely outside sprints.
-
Safe mode is available from the "manage add-ons" section. It disables all your add-ons, with the idea being you can prove basic Confluence works and then you re-enable add-ons one at a time, until it starts to crash again, and then you know the last add-on you re-enabled is the problem. However, if it is ScriptRunner, this…