Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! Confluence is a wiki, so there's only really two things you will do with it - find and read stuff people have written for you to read, or create content. There's not a lot more we can tell you about how you would use it - best thing to do is just get stuck in - use it to do what you…

My first real job (meaning I applied for it and did all the work, rather than my relatives handing me things that I consider to be internships or one-offs as a favour), was a retail job. I stood behind a till for a month, taking money from people for goods. It suited me well at the time. I got to talk to lots of different…

This dopey little melt likes "helping" when I'm coding. Fortunately, Atlassian sent her a Cloudie to distract her.

Welcome to the Atlassian Community! Confluence server dies early February next year. It will continue to work, your server licence is "perpetual", but all support for Confluence server stops then, and you won't be able to upgrade your Confluence past the version that is the last server release. This does not mean the end…

Welcome to the Atlassian Community! Generally, things will use the REST API to create Jira issues such as tasks. There's a lot of software that can do this, once given some connection settings, and a lot of them are for doing different things, so they trigger the creation in different ways. I think we need to know what you…

You have given admin rights to someone else, who has now locked you out of it. Or, you have let the site lapse (no one logged into it for a few months, so Atlassian have shut it down). Either way, start by going to admin.atlassian.com and having a look at what products you have (it'll tell you where they are) and what…

Welcome to the Atlassian Community! No, the "status in column" thing is the entire point of a Kanban (or Scrum) board. If you're finding people are doing things outside Jira, then it's most likely that your Jira is not set up to match their real-life processes. If you fix that (by "flexing the columns and swimlanes" as you…

Welcome to the Atlassian Community! Atlassian still fully support the use of Sourcetree with Bitbucket and other git management systems. Could you tell us what exactly was said on that issue? Bear in mind that the Bitbucket team do not support Sourcetree, it's a different team, and it's not a case of "Bitbucket supporting…

Off the shelf, no, there's no way to do this. The closest you could get would be to automate the creation of a link when someone leaves it blank.

If you changed the context of the rank field, setting it to be valid on all projects except this one, you would blank it out. But, this would destroy the ranking of all the issues in the project, and when you changed the context back to global, the issues would again be ranked at the bottom of your backlog. Your best…

Welcome to the Atlassian Community! Yes, Jira is an Atlassian product, and the community would love to help you. But we can't. We're not the administrators of your acsjira, and you need to talk to them about your access to it. The error you are getting is an internal error and it needs them to read the logs to find out…

Welcome to the Atlassian Community! First, what @Fabio Racobaldo _Catworkx_ already said, I don't need to repeat it. What I wanted to add is that you really need to read the application logs. If your apps are behaving wierdly or losing data, then there are going to be errors going into the logs that tell you what is going…

Most of us try to define status with names that says what they are, and Atlassian does the same with its defaults. "To do" means the issue needs something doing about, "In progress" means it is in progress, "Done" means it is done, and so on. Status are configurable, and you don't have to use the defaults Jira gives you.…

Ok, licence management of Jira users, or licences for other systems?

Yes, you can create whatever measure you want. Most people use the sprint estimate (and that's usually story points or time estimate)

Jira Software was built to support Scrum and Kanban. With these, a board generally represents a team. Your people going off and creating their own boards is not a problem, but if they're creating their own sprints, they are not working as a team. There's a whole load of things I could address individually in your question,…

Apps often add their own dummy users, which don't count towards your user licence. To create a dummy user, you will need to pretend that the dummy is a human - they'll need their own email address (which you can access), and you'll need to run through the same process that you did to create your own account.

Welcome to the Atlassian Community! This is what it says it is - someone in your organisation signed up for Jira a while ago, but none of you carried on using it, so it went dormant and is now about to be deleted. This won't affect your Bitbucket usage at all. It is just that the Jira instance will be going away. It won't…

Welcome to the Atlassian Community! The usual way to do that would be by adding a "filter results" gadget to the dashboard.

Welcome to the Atlassian Community! You could remove the ranking field from the project context, which would effectively blank it out, but that would mean all those issues appear at the top or bottom of your backlog unless you added something like "and rank is empty" to your board filters. The best thing to do here is…

Clone does what it implies - makes a copy of the original. Moving an issue to a different type or project is a structural thing that cannot be automated - a human really needs to look at the issue when you move it. Generally, you should not be trying to clone issues into other projects (and if you do, you need to "clone…

There's no confusion. You have been restricted away from your repository by another admin, or it has been removed (due to inactivity, not paying the bill, or an admin removing it)

Yes, that is correct, since February, you can not buy new licences for apps, because all support is going away in less than a year. Whilst Atlassian is going "cloud first" as you say, there is still the data-center option, which is not going away any time soon. If you move to DC, you'll be able to get almost all of the…

Welcome to the Atlassian Community! You do not. The steps are completely necessary when you make a structural change like changing between issue types that are configured differently. You can minimise them by making the field and workflow configuration the same for each issue type.

Welcome to the Atlassian Community! You can't do this. Moving issues is not something that should be part of an operating procedure, it should only be done for housekeeping, migration and in the rare times that an issue has been created in the wrong place. Jira tries to keep move as simple as possible - it only asks for…

No, issues spilling over from one sprint to another just means that your team is getting something wrong or have had an unanticipated problem during the sprint. Churn happens when you are not planning properly.

No. It's horrid. Whilst it can work for some basic stuff, it fails, and fails hard, at specialist subjects The Atlassian Community has banned three people who have tried to hook up a crap AI to it, and even today, I've hit a fourth trying it on. It's not that the AIs are making bad posts, it is that they are wrong.

I'm with Dave on this one - people first, process second, your choice of tools should fall out third (and as the Atlassian fanboy, use the Atlassian suite that is built with people first. But do not do that unless it is right - do what works best for you)

Indeed, "getcustomfield" needs the issue context. If this code is in a post-function, it will have that context, but it still needs to go back to the issue. The starting point would probably be def number1 = issue.getCustomFieldValue("Impacting") (But that does assume a whole load more stuff that you might need to check…

Welcome to the Atlassian Community! No, you can not allocate someone who cannot be identified to a task. It can't work - if you don't know some basic details (like having an account), then you can't uniquely identify someone as an owner/approver or anything else.