Nic Brough -Adaptavist- Expert

That error code is just a reference for Atlassian support to be easily able to find your system and the errors in the Cloud logs. You need to take this to Atlassian support if it persists, raising it at https://support.atlassian.com/contact

Confluence doesn't care where you log in from. As long as you are not sharing the account with many people, you can log in from as many places as you want.

That would be a very very bad thing to do because it completely breaks all concept of ownership, traceability and responsibility. Which is what Jira is for. Your "requirement" is wrong, you need to change it.

For Confluence, space export and import (see "space settings") will do it. For Jira, it's more complex. When you say "copy project", do you mean the configuration and the issues, or just the issues?

Yes, you can import fields from Redmine, as well as attachments. There's no import of users directly, but you can tell Jira to create missing users from the issue data. If, for example, you don't have Bob as a user in Jira, but your import data has Bob as a reporter, assignee, authoriser, participant etc, Jira can create…

The only fixes for this are to simplify and hence shorten the javascript needed (that's an Atlassian task, as the coders of the software) or to get a faster browser (which is unlikely to happen unless you're using a microsoft one)

No. Email addresses should be unique and distinct, it would be wrong (and in some fields, illegal) to have the same email for different accounts.

If you were on a commercial licence, you could raise a support request for Atlassian to change it. As you're on a free version, that option is not available. You will need to subscribe to the new Cloud system, remembering to choose testrobomq as the name for it, then export your data from your current system and import it…

I forgot the question about the thing that comes with me. Obviously - the cat. But the better answer is the penguin. It's a really battered, faded, one-eyed penguin soft toy with a long story. My grandma gave him to me when I was born. It's always been there, and probably always will be.

Sister is better now she's 40 with her own kids, they've enabled her to understand she was a right royal pain (to be fair, it was only until she learned how to express herself coherently, once she was able to "talk" to me and I could translate it for the parents, she stopped being a nightmare child, and then when she could…

I've got a few moves - * When I was born, my parents took me back to a house in Heaton Mersey. * We moved to a larger place in Stockport to allow for the other three kids they claimed they wanted (they changed their mind and stopped at two when my sister was born because she was a bloody nightmare baby) * Then we moved to…

Jira only supports Issue -> Sub-task. (Note that I'm using Jira-speak here - you can have many different names for the issue and sub-task types. Almost all of us have an issue type called "story" at the issue level. I'm talking about layers or levels here, not specific named types) Jira Software enables Epic -> Issue ->…

You may own a valid licence, but this message means that the one in Confluence has ended. Check your Atlassian account and apply your "active licence" to your Confluence (should be a copy and paste" action)

* All Jira Software fields are available via the REST API * If you mean database schema, no, you cannot get anywhere the database on Cloud. You can add whatever custom fields you'd like though * Jira fields do not have access control, barring a couple which have some permission control (reporter, assignee and due-date for…

No, there's no way to do this yet, the segments are not configurable

You don't. Cloud only has one priority list, and if you add your customer's priorities, you've got a problem in that you will have all six priorities showing for *everyone* If you go off and use a different field for this one customer, and want to "translate" existing priority into it, then run a search for "project = X…

You would need to write all the code required to place them there, and then get Atlassian to implement it in Cloud. Better would be to request Atlassian do it.

Yes, that's right. For a project, Jira numbers the issues on a simple flat "add one to a sequence" rule, so if you import issues into an existing project, it's going to renumber them starting with the next free number. So imagine you've got an import with 100 issues in it, numbered between TOOL-1000 and TOOL-1500 (missing…

Multiple assignees, yes (assignee in "Alice, Bob, Charlie"), but it will be a single item in the list of quick-filters, and the results will be issues assigned to anyone in the list.

What do you mean by "module"?

It depends on what you are doing to "merge". In the most simple case, you could just take all the issues from Tool(xyz) and import them into Tool(abc). The only thing is that the incoming issues will be renumbered as they're added to the target project. If you don't want the xyz issues in the target abc project, you'll…

Indeed it is. Create space is limited to administrators and anyone in the group(s) named for space creation. I would ask your admins to add you to the global "can create space" permission.

How are you triggering the transition of the other issues? It sounds like you may be using a script that does not re-index after the transition somehow.

I'm afraid you'll need to look back at the process here. There's a problem with what you're trying to do (which is partly why you're struggling to get to what you want) You say (with my emphasis added): "I'm looking to create a sprint Burndown Chart (using story points) filtered by both assignee and for subtasks only." The…

Stops people overloading them and making them too slow to be useful though.

You must not just "set" the status. That is only appropriate when creating new issues, it does not work for existing ones. You are going to have to tackle your travelling salesman problem and work out an optimal route through the workflow to your desired point and issue a number of transitions to get there. Fortunately, in…

Service Desk projects are intended to be used by Agents, not by customers or (for want of a better word) Developers (Jira users who are not agents). The project is there to communicate with the customer, the Agents being in control of the communication and process of handling the request, with Developers only expected to…

Your mail service is set up to require TLS, so you need to enable that in the connection Crowd has with it.

Removing the init file worked because it is confusing the startup systems in Linux. In many of them nowadays, there's systemd and init.d, and you really only want one of them to be used for any given service. If something is set up to be usable by both, then it gets confused. I try to stick with one only on any given…

Bitbucket (meaning really the git behind it) stores and tracks files. I suspect your "documents" are files, so all you have to do is add them to a directory Bitbucket is looking after.