Nic Brough -Adaptavist- Expert

Check the notification scheme for the project. What is the rule for selecting people to notify on the "issue commented" event?

Which Test Management app are you using for this?

Ok, then you can drop the Core install (assuming it has no data you need to keep) and just do everything in the "Software" installation.

Sort of. You can expect it to be gradually deprecated over the next couple of years, as most corporates with regulation/compliance meaning they're sticking with Server/DC really don't want basic authentication, and everyone else should be on Cloud (which doesn't have it). I would move to Oauth access to start with (over…

This is the bit that my anecdotes are all based on You say "teams that don't have a "I thought the other one was doing it" problem". Show me one of those and I'll show you a handsome invisible pink unicorn. Granted, some teams are better than others, and many superb, but it will happen, in every team, eventually. The…

Yes, application links between them will enable some functionality. Doesn't matter about what the platforms are as long as the networks let them talk to each other.

Cloud has been having ID problems over the last couple of days. People not appearing in groups they are defintely in, which, of course, affects permissions. I suspect it is that.

This would suggest you are "only" a customer, and not a Jira "user".

Ok, I see where your error is. You think time should accumulate up to Epics. Not estimates, which is what Scrum works with (of course, time is one thing you could use as an estimate) You do not burn down on time, you burn down on estimate and completion. That's why the Epic burn down is not showing you anything - you're…

You need to clear the resolution field of any data. Normally, a "reopen" transition will have a "clear resolution" post-function on it, but if an admin builds their own workflow or re-purposes other transitions, they can easily lose it. Two steps - * Edit the workflow and add a post-function to "re open" transitions - you…

You have taken a copy of a Confluence database and pointed the wrong version of Confluence at it. Stop your test Confluence. Go look at the exact version of Confluence that your data came from. Go find a download of the exact same version of Confluence, and install that on your test system. This will fix the error, and put…

Possibly. I need to be very clear on what you have installed. Have you got Jira running twice? One Core and one Software? If so, then yes, you can drop the Core installation (assuming there's no data in it you want to keep). The Software install has all the functions Core has, because it is actually Core + Software.

Oh absolutely - unless you've done a scrum course, or you're in a (real) scrum team and had it explained properly, you will not understand estimates. Swimlanes are often misunderstood too - there's at least half a dozen of my answers here including a phrase like "I think you might mean Columns, not Swimlanes". I prefer…

You need the project level permission to delete (not admin - admin rights give you the permission to administrate, never "do anything" as that's a security nightmare). So, two things Look at who has "delete issue" permission in the permission scheme for the project. Add yourself Do not delete issues (yes, including…

I do not understand what you are asking. There is nothing to "cater for" here - you cannot restore databases like this. If you're doing an upgrade, you take an existing, working Confluence and upgrade it. If you're doing this on another machine, such as a test server, then you start with a copy of the existing working…

A group-picker can also be useful to indicate other people to talk to. But multiple assignees does not work in real life. You will always have "I thought someone else was doing it" and makes it impossible to track progress or work.

Atlassian are not going to rewrite the REST API interfaces for custom use. Also, you should plan for Basic Auth to go away. It's been removed from Cloud, is on the way out on Data Centre, and Server will follow shortly after that.

Absolutely - SQL is the last approach to getting data, never the first.

You cannot do it directly. Jira people are generally added to a project by role, and Confluence does not have roles. If you are using groups in Jira though, you can do this by saying stuff like "group X gets browse project in this permission scheme and create permission in this space". Add someone to group X, they get…

I am not missing the point, I am explaining what you are seeing and why it happens this way. I know it is counter-intuitive, I know you've seen lots of places (try to) work this way, but it is wrong and hence Jira does not work when you do it. The estimates you put in front of the product owner, and hence commit to, are on…

You will need to amend the "create" screen for the issue type, adding "summary" to it, so that one can be added during creation. You cannot have a Jira issue without a summary (your test cases are a type of issue)

I think you've misunderstood. You are absolutely right that Scrum does proscribe that you estimate backlog items. What I think you have missed is what a backlog item is. It is something that your product owner would like you to do and an item that you can commit to doing in a sprint. Not a sub-task. Sub-tasks are a…

Ah, that has just kicked me in the memory! Thank you so much. It absolutely is coming from ScriptRunner. It is there to try to give you the option to see the sprint, or backlog, that is currently in front of you. But I think the complexity and an oversight is misleading us here. I have certainly mis-read one of your…

Yes, our option for single column and easily relocatable sections have been removed. Why? I can't say why anyone thought this was a good idea.

So we need to be very clear about what you are doing. It's fine to have a load of different status, but my first question is "why are you not reaching the 'done' status by the end of the sprint"? The whole point of a sprint is that you commit to delivering a set of work-items by the end of it. If you do not, you have…

My guess would be that the issues you are "missing" have a "fix version" set. Scrum boards use that for "we're aiming to fix that in that version". Kanban uses it for "we released it". The boards, while looking similar on the surface, do have different purposes and behaviours. From what you've said here, I actually suspect…

Yes, that's what you should do - create a filter that returns what you want to see, save it, and use it the filter gadgets that let you use what you want to.

Yes, I know, this is a bit of a pain. There are four factors here * Jira and Confluence are separate. Even if you've got the same user directories enabled and shared, and even when SSO is enabled. They're separate systems. * They have different permissions. Jira has "project roles", Confluence does not. Jira has…

Actually, no, you should minimise database change as much as possible. You can kill off most email access by amending the setenv.sh file in the bin directory of the test install. See https://confluence.atlassian.com/adminjiraserver073/restoring-data-861253828.html#RestoringData-1.Disablingemailsending/receiving

Ah, I think I know part of the answer. That blue icon you are clicking is being injected by one of your apps, and it's doing heck-knows-what. None of the Cloud or Server (or the DC) installs I've got access to have it. I think we need to find out where that is coming from and what it is supposed to be doing.