Nic Brough -Adaptavist- Expert

Synchrony needs to use "websockets". I'm not going to pretend I understand the mechanisms that describes, but I do know how to make it work through a proxy. I tend to only work with Apache2 (and you need to be on 2.4 or above for this to work) This system has offloaded the SSL to Apache, and the Apache is serving up a site…

The application and error logs will report on login failures. If they are not logging the attempts and failures, then you've either turned off the logging, or the login request is never reaching Confluence. Check all the files in <confluence home>/logs (start with atlassian-confluence.log, but you'll want to check most of…

You do not. Jira does not have field-level security. There are a couple of apps that enable some form of field-level security, but plain Jira does not do it at all. It only goes down to issue-level security.

Thereby making the assignee field pointless, and responsibility really hard to track and identify. Don't do that.

Could you explain what this has to do with an Atlassian system?

You will need to look at the various scripting apps, to add scripting/coding conditions.

Monthly, last time I did it.

But which one is responsible for getting it done? What stops either of them saying "I thought the other one was doing it". You should never allow people to put themselves in a position where it's valid to say that.

Attachments are not a field or a field type, they're a function that allow you to add files to an issue. If you offer attachments to the humans, it really is just a simple open area with a pile of files in it. There are apps that add functions to the attachments, so that you can categorise, sub-directory and/or label…

1. That suggests the issue is only in one sprint. 2. You can only drag forwards in the columns because your worklow either doesn't have transitions to other places, or, if it does, they are protected with conditions (on the transition)

All the places that you maintain screens and schemes take the form of lists which give you information about usage. Some of them have a system which splits the list into two parts - "active" and "inactive", which is not a flag, it's an indicator of whether the item is in use or not. You can expand the "inactive" section…

No, it's really bad practice to have multiple assignees. It's fine to change assignees as responsibility over time can be different, but you should never never have more than one person as the assignee at a single time. And, yes, absolutely fine to decompose, or put "and other people may be involved" fields in, but the…

Jira is an issue tracker, not a documentation system, it's not got functions for creating ad-hoc blocks of text. But most Jira users will use it hand-in-hand with Confluence (which is a wiki)

Issues are only deleted if a human deletes them (or the project they are in), there's no automatic deletion.

Check the permission scheme for the project the issue is in - do you have Edit and Schedule issue permission?

Only project administrators (and of course, system admins) can add components to the project's component list. Have another look at the project permissions, you'll find everyone who gets the option to add a new component matches the "Administrate project" rule, as…

Not yet, priority schemes only exist for Server/DC at the moment. https://jira.atlassian.com/browse/JRACLOUD-3821 is the request (the votes are slightly inflated - when Cloud and Server diverged, this one was cloned from the server request, which was eventually implemented, so some of the votes on the cloud one are…

Sorry, there's a lot here and I missed that bit! Thank you! So, if you can't set sprint, then there's either none that could contain the issue, or you don't have permission to set the sprint. I can't think of another way to block that field in company-managed projects.

I'm not sure where you are lost on implementing it. It really is as simple as having a workflow that covers the end-to-end process (new through to complete) and telling the boards to look at different bits. Let's say you've got a single project and the process is just: New -> in-dev -> dev-done -> verify -> Complete * Your…

Could you tell us what type of project you are working in here? In most views of the project, the left-hand side panel will say "team managed" or "company managed" (There's a couple of ways of setting up projects to get this "sprint = none, and uneditable" behaviour, but I don't want to waste a load of time explaining the…

Ah, good point, I hadn't thought of that. I suspect it's ok, as you could easily argue people like Adaptavist and other (less Atlassian) consultancies do it indirectly. We regularly fire up Jira and Confluence pairs to help communicate with our clients, and as we're getting paid to work for them on their projects, you…

Um, actually, only admins get to see the full list of projects. If a non-admin user doesn't have "browse project" for a project, then it won't be shown to them in the list of all projects, Jira hides it completely. But the security needs there are definitely things to think about.

No, there's no "inclusion" here as you've used it. I think it might be easier to explain from the bottom up. The Atlassian Server and DC applications can be thought of as "platforms" upon which you run plugins/add-ons/apps. There are four ways you might use these: * Built-in and "system" - a lot of the functions in Jira…

Nah, it's not breaching any terms of service, you can invite whomever you'd like into your Jira/Confluence/Bitbucket etc, from any organisation you want, and then segregate them by project/space/etc as well. Your main worry if you're going to do this is the "leak" between the various people and organisations, they can't be…

Yeah, it's actually an accident, it wasn't designed to do it, but it allows for it. It will, of course, still break all your scrum boards and reporting.

You don't "map" boards together, that makes no sense. Nor do you "move" issues between boards. A board is a view of a selection of issues, not a container. You can meet your need though, it's quite simple - tell the scrum board to only select issues in the status up to and including "dev complete", then tell the Kanban…

There's well over a thousand, I'm not sure a list would be of any use to you. But if you really think it would be useful, start at https://marketplace.atlassian.com/search?hosting=dataCenter If you're migrating to DC, you'd be better off simply reading the list of "user installed apps" in your Server - you only need to…

Ah, I see. Many done status has always been possible in Jira Classic/Company-managed projects. How are you doing "done" in many status in team-managed projects?

You'll need to ask the project leaders what to put in (you may not need to be assigned, but the Jira ID is a reference to the story under which your work should be tracked)

Your table is not a board. The only way you could get close to that on a board would be to have a workflow where the status of an issue actually represents its issue type. Which would be unusable as an issue tracker! Your table is probably more of a plan, so I'd be looking at Advanced Roadmaps or Big Picture to get that…