Comments
-
Shut down JIRA and Confluence, clone the databases over to their targets, then edit the connection settings in <JIRA hom>/dbconfig.xml and <Confluence home>/confluence.cfg.xml to point at the new databases
-
Thanks for the explanation.First, make sure that your government owners have Atlassian accounts, then find out what they are (usernames and emails they are associated with)Next, contact sales-at-atlassian.com, explaining that you want to move the licences from one account to another, giving them the old and new accounts,…
-
Define what you mean by "transfer"
-
No, sorry, they have to be an administrator.
-
You can only run one service per port, so if Tomcat is on port 8080, then nothing else can be. Jira runs inside Tomcat as an application, so if Tomcat is on port 8080, you can tell Tomcat to serve it up under port 8080. What you can't do is have two Tomcats listening to port 8080.
-
Atlassian have pretty much said "no". See https://jira.atlassian.com/browse/GHS-8975
-
Correct, you can't have it both ways, and AND is *far* more useful choice when you can't.It would be nice to be able to use OR instead, but you'd need a *very* clear way to display it.
-
No, the filters are deliberately set as AND, and they do try to show you that they are selected many times. I suspect that with a bit of code (possibly even just javascript), you could change the behaviour so that when you click one filter, it automatically deselects the rest (although you're then going to find people like…
-
>It asked me to enter a key or to continue in evaluation mode. I chose the evaluation mode. It asked me to restart my server. I did. When you do this, it should have asked you to connect to your Atlassian account to create new licences. It sounds like you already had an account, with licences that are too old. Go to your…
-
Not really. A Kanban board is a Kanban, and it's not really compatible with Scrum. There's no way to "convert" them. But you can easily set up a new board that uses the same filter to select the same issues, and make that a different type. (Then, delete the old board if you're not going to use it)
-
We can't tell you what you or Cloud has done "wrong" from that description. "However, it showed an error regarding the license activation." is a bit like saying "my car won't start" - we don't know if you've lost the keys, dumped it in a river, run out of fuel or been attacked by a horde of annoyed penguins and can't get…
-
It is exactly what the error message says it is. You have too many users and have exceeded your licence. Either get a licence for more of them, or reduce your active user count. Your administrators need to do that, I'm afraid we're a community of end-users, not your admins.
-
If you aren't willing to use the permissions, then yes, your only choice is, as I said, multiple servers. With the option of synchronisations
-
JIRA and Confluence have no notions of "DMZ". They provide users access to issues and pages. What you're trying to do is completely supported though. You grant * access to the world (but with a login required) * your internal users access to all spaces and projects * your external users only the access they need If you…
-
Yes, but it's not a "change", it's currently "get new url, export data from old one and import into the new one". See https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html
-
I'm afraid not. The problems are not actually in JIRA, so Atlassian can't really do much with it. I heard that there are some issues with it that are rooted in the way Java does things (for which there are some coding tricks/standards and workarounds), but the main issue is that the drivers themselves are the problem. So,…
-
If Mirek's link doesn't answer it (it's what I was going to post), then you'll need to explain what's going wrong and how you've already tried to do this?
-
Ahh, that explains it. Not quite - if an issue is assigned to XY and you assign it to you, then Jira will generate an email to send to both of you. But it will drop the one it's going to send to you because it was you who made the change, and you've got "don't mail me on my changes" flag set.
-
That doesn't sound right to me. Jira doesn't treat "assign" any differently from any other event when deciding on recipients (Although the assign event does treat "assignee" as both old and new assignee) I suspect you've got something in the assignee notifications that is causing it - what do you have in the notification…
-
Screens are a list of fields to present to a user when an action is taken. The mandatory flag is a flag to say "this field must be filled for the issue" You have set up a situation where you're demanding a field be entered, but then not giving the field to the user for them to enter it. The screen and field configurations…
-
No. Atlassian dropped support for IE8 a while ago, when it became clear that it was not going to be supported by Microsoft. Your organisation MUST move to a later version of IE soon, as MS will no longer support IE8, let alone Atlassian. I'd aim for IE11, or better yet, a proper browser, as that will give you a bit more…
-
No, I'm not sure why it's doing that! I wouldn't expect to have to link an Epic to anything! I'm a bit stuck :-(
-
I'm not sure what the "jira item editor" is - do you mean "Edit"? Anyway, you cannot edit issues that are in a status that has a flag of "do not allow edit in this status" set on them. You'll need to re-open the issue (which, if you've got a correctly designed workflow, will blank out the resolution), edit whatever needs…
-
TEchnically, no. Properties belong to users and you're looking at issues. However, it's quite easy to write a field that will extract that data, and there's even a field to do it in the "Jira Toolkit" plugin. However, you need to think about usage. Specifically, which user's properties do you want to appear? (I think…
-
No, it's generally not a good idea to duplicate data like that. When you do need to do it (And there are genuine times when it's useful, no matter what your structures), you should be doing it manually, because it's not going to happen very often and you usually want to think carefully about how you do it. My current…
-
Try one of the links it says the page may have moved to. Atlassian often move their documentation around, and Confluence has the function to tell you where it has gone!
-
OK so if I understand this right, you can ignore the default screen as it's not relevant. Your transition and view screens are the same (not just similar definitions, but the same screen). Is that correct?If it is, then I would like to check my understanding of the problem - that you enter data in field x in a transition…
-
I'm not sure what you mean by you've "you have to make sure the screen is set to view" in the screen scheme. To go over it quickly, a screen scheme tells the project which screens your Jira project/issue-type uses for the actions of Create, Edit and View. This is not related to your transition screens (although there is…
-
It's partly historical. Back in a very old Jira, there were no hooks in the workflow for Conditions or Validators - the "does user have the close permission" was almost hard coded into the workflow, so all you needed to do was add it and not worry about the workflow. The newer system where you explicitly add your own…
-
See https://confluence.atlassian.com/display/JIRA/Linking+to+Another+Application As for version - use the latest.