Nic Brough -Adaptavist- Expert

Ah, I see, I did not understand that at first. Yes, that would be a nice function to have in the diff screens.

There are a couple of server apps that enable "locking", and may help with merging changes, but there's nothing in the core. Confluence is aimed at being a wiki, not a document management system.

You're right, I'm exasperated and frustrated that you and others are refusing to understand it, and that makes for grumpy and terse responses. I've read the links before, they simply confirm everything I've said, or don't mention the subject. I can't help you understand "estimates are measured against committment,…

Ok, most of that is a waste of time because you're just rehashing arguments against it all again that either show you don't understand the point, and are mostly built off your complete failure to grasp the most important thing I've said "Yes, that's correct, sub-task estimates are not part of the sprint. But they are, I…

Burndown does not measure sub-tasks, as you do not commit to doing them in a sprint, you commit to their parents. So, no, you won't get sub-tasks scored, estimated or burned down on.

I'm going to take a guess that you've run into a long standing and annoying flaw in thw workflow editor. The draft edit can not add transitions to a step (status) that does not already have outgoing transistions. There's a long essay possible on where the problem is, but Atlassian have said that fixing it is way down the…

The very nature of attach, download, edit, upload means that you simply can not collaborate simultaneously on a document. The simple solution is to import the word document as a Confluence page (or set of pages), then you'll be able to collaborate on it in real time, and your edits will not be replacing each others.

Yes, if you are using classic projects. Do you know if you are working in a classic or next-gen project?

You could set the board filter to say something like "and !(status = done and issuetype in subtaskIssueTypes())", but this creates the problem that your sub-tasks, as part of their parent issue, cannot be done, so you won't be able to finish anything. A better option is to live with the fuss on the board but give everyone…

Depends on what you do to "transfer". Could you explain more about what you want from this, and what you have tried?

It is triggered when you change the project. That's what the log is for, it catches project updates. I think we might be talking at different levels here. Instead of go around in circles, could you tell us what you trying to achieve here? What are your users going to get out of whatever you're trying to code for?

Think of it this way - why would a later version deliberately remove a critical security fix? Apologies if that sounds a bit snarky, but it was the shortest way to put it without a boring essay question. Every version after the ones Atlassian say fixes were released in should incorporate the fix, as they're based on the…

Issue updates are not project updates. You already have all the project updates in the log.

I would stay well away from this, it's not really a good design. I would turn the question on it's head, not necessarily asking "why this design", but "what are the benefits of having this document id?". The document is a Jira issue, which already has a unique ID that is more useful (you can search for it directly rather…

Yes, but it is by project and issue type (as it can vary by both). Annoyingly, this is for Server directly, but the same calls and principles apply to cloud - https://developer.atlassian.com/server/jira/platform/jira-rest-api-example-discovering-meta-data-for-creating-issues-6291669/

A lot of us have used "subscriptions" for this for many years. If you run a search for issues you are interested in, then you can save it as a filter and in the options, hit "subscribe" which will take you to a set of options, so you can tell it to email you whenever you want. I've usually gone for a "sunday night mail"…

That's not what the audit log is for. The audit log is to record administrative actions, not day-to-day issue tracking. The "audit log" for issue create and update is on the issue, as that's the main reason Jira exists. 

It's no good saying "I got your point" if you're just going to post a string of stuff that makes it clear that you have not. I can't think of another new way to explain it again, I've run out. I can't understand this for you, I suggest you have another read and think it through again. I'm not going to try to pick and…

Australian English is not available on Cloud I'm afraid, but it's a lot closer to English than American English is, and the main differences are in words you probably wouldn't find much in an issue tracker! Obviously, the date format is also correct, so you can get very close to Australian English this way.

Hmm, I'd expect it to be asking for a Jira server before "component". Can you check that you have linked Confluence to a Jira system?

The project name is not a component (unless you've deliberately added a component with the same name as the project). I think you might not be using the right words to describe your problem. Could you give us a screenshot maybe? Or describe what you're clicking on and getting?

No, you can't turn it off (yet). But you can * Go to profile -> Manage Settings -> Notifications and turn off the emails about them * Ignore them There was a thread recently about this on the original "badges are new" thread, which explained those two options, and there's a note about investigating other options in Khoros…

No, you can't turn it off (yet). But you can * Go to profile -> Manage Settings -> Notifications and turn off the emails about them * Ignore them

There shouldn't be any need to go through a mid-step here, you should be able to jump directly from 8.0 to 8.14, and from any version of 8 and lower (in fact, I've seen 7.12 go straight to 8.14 without any hitch) I think we'll need to dig into the errors you ran into a bit more.

Ok, that means it's taking too long to start the apps up. Jira Software and Service Desk are quite heavy and the usual problem here is that they need more resources, or at least time to get things started. If you click "learn more" you should land on a page all about resourcing and time to start up.

I am very unclear on what you are doing here. "Data type" suggests you ned to add a field, but then you describe post-functions, which are actions taken on transitions in the workflow (ot status). Do you mean you have a custom field that you want to update on each transition? If my guess at that is right, then you'll need…

Actually, this is likely to be down to a long-standing bug and it's not quite the counter. You should find that none of the issues listed have had their keys changed, what is happening is something is creating an issue, getting far enough through the process that it takes the next key but then falls over, not actually…

Usually when people ask you to do that, they'll give you a little guidance on what to include in it. Our lot has "create a profile page and talk about about yourself, get a photo in it so people have a face to spot, mention places you've worked (so if they come up as clients...), and broadly what skills you bring" - it's a…

Trello and Jira are two different systems for doing two different things. One is effectively a pin-board, the other an issue tracker (you can use a pin-board as an issue tracker, but it only has a few of the features) I'm not sure what your boss is thinking of when he says "integrated" All this change is about is that your…

Complexity of the task across the services, plus building a decent front-end UI and supportable policies for it is adds up to a chunky bit of dev time, and they simply have other priorities.