Nic Brough -Adaptavist- Expert

That's the attachments, Confluence works fine with huge numbers of pages, that's what it's designed for.

It's the same as it was in November 2017 above. Cloud recently announced they could do a full rename in the config now, I don't know if that will make its way to server.

It is all quite involved, with three things you need to look at for custom fields. To try to keep this simple, I'm going to answer your questions in totally the wrong order! To get a custom field put in front of a user, it must * Be on the screen they are using* This is the simplest bit - a screen is just a list of fields…

Could you describe exactly what the symptoms of "doesn't allow me to do this" are? You say "On the left we have the "add workflow" which is for some projects working and for some not. " - that's where we need to know what is wrong - what does "... for some projects working and for some not". What do the "some not" projects…

How are you telling Jira that it is "critical"? Why is that not the information that something is "sev1" already?

Project admins can only trash the team-managed projects that they own. Company-managed projects can only be trashed by Jira and Site admins. You can't stop project admins from being able to trash their own team-managed projects, it's one of the points of being team-managed.

I've added it to Atlassian's "need to check (and kill) malicious site" list.

Global permissions don't have anything to say about space access beyond "can log in". I think you've run into the "in some cases" thing here - because your developer account is also the customer account, and Jira and Confluence both know that, it is thinking "well, they can see it as a customer, and they have logged into…

You have not explained where you are stuck. Before we go any further, I'd like to take a step back and confirm that you are trying to do this in the most suitable way for your systems. The doc you have pointed to is about making Tomcat handle all the SSL, which is quite complex and imposes load on the Tomcat servers that…

@Yasser Al Kindi - it does use Agile terminology, but the software is an issue tracker, it was built for more than just Agile. If you use Scrum or Kanban Agile methodologies, then you'll find the default terminology there is agile - for example a standard default scrum project will have issue types of Story, Bug, and Task…

Again, you do not transfer sub-tasks between sprints. Sub-tasks are not sprint items, they're only in a sprint because their parent is - they are a part of their parent story. The parent story is not done if it has open sub-tasks, and when that moves into the next sprint (because it is not done) all the bits of it move…

So your added clauses are incorrect for some reason? What are they doing wrong? Could you give us the whole query? My guess though would be that you've misunderstood the order Jira will execute each clause when you have a query that mixes ANDS with ORs. (We all do badly at that, it's hard to understand what Jira is…

Please re-read the last sentence in my answer. The view screen doesn't actually matter - Jira will always display the resolution, whether you have it on the view screen or not.

But you could have a sub-task type called "task"!

Um, yes, each issue type has its own icon. Why are you posting the list here?

No confusion, just meant I couldn't be sure that the first script that search finds is the most appropriate. It is though!

It's what queues are for - support call comes in, 1st line needs to hand it over to another team, the other team should be monitoring their queues. They don't need to sift or team-assign, the queue should be set up to organise it for them.

Welcome to the community! This looks right to me. Administration rights are for administrating the system. They are not project permissions (project or security) or notifications, and they're not there for sharing things with either. Most admins will be on other groups or roles that give them the permissions, mails,…

Another question is "what is actually stopping you"? What are the symptoms when you go in to map a new workflow in the workflow scheme for the project?

Issues can only be assigned to a single user. This is correct behaviour, multiple assignees or group assignees never work in real life and often make a complete mess of simply getting things done. There is absolutely no problem having associated people or groups though - "If the assignee Charlie isn't around, you can…

Epics can't contain other Epics. To group Epics together, you'll need to go up to Initiatives and Themes. A link saying "parent/child" is not a parent/child relationship as far as the software is concerned, it's just a link.

Welcome to the Community! I think you may be in the wrong place. It sounds like you need help with your Confluence, but you've clicked on "help with Confluence" and ended up in the Community. We're not your Confluence admins, you probably need to be talking to them, not us. We've got less access to, and less knowledge of,…

Yes, it's just because the Atlassian checks on new users can be passed by 'bots, there's not quite enough checking and some can get past them and hence create spam-generating free servers. There's nothing Atlassian can do other than shut down malicious machines when found, not without imposing harder checks on the "people"…

No, there is no "mark specific status to imply it is resolved". The Resolution field tells Jira whether an issue is resolved or not. You need to look at the workflow, and probably edit it. First, list out all the status, and group them into "finished with this issue" (end status) and "still needs attention" (needs work).…

It's never been possible, you have to give the Epic name AND Summary on the create issue screen for an Epic. The closest you can get is to choose which one you want to keep and write a post function that replaces what the user enters with the content you want to keep.

Atlassian has a bit of a problem with their Cloud model - it is vulnerable to malicious users (in fact, almost entirely 'bots, rather than humans) setting up free Atlassian accounts, and then setting up free instances of Jira/Confluence/Bitbucket and so-on, and then host malicious files and send spam from them. If you've…

Welcome to the Community! If you are planning to use Story points for Scrum, or Agile planning, then you need to be very very careful about this. Get the Story Points added to your Stories as @Floki says. Do not add them to sub-tasks. This will break your sprints and reporting, rendering your story points useless. Think…

The swimlane function lets you choose from several items to define the swimlanes - Epics, stories, assignee etc, but all but one of these are hard-coded. Customer is not (yet) one of the hard-coded options. The last one is "JQL", which is less hard-coded. It lets you define your own swimlanes, and you can use any search…

There is nothing in Jira that could do this, the browser must be doing something really odd. Clicking "back" effectively refreshes the navigator, it doesn't trigger "download the html of the page to your machine and upload it as an attachment on an issue". Yes, I'd try clearing the cache, but I can't work out how the…

There's a bit of a complex explanation to this, but I believe you can do it, in some cases. Imagine you have two people - a customer and a developer. (I'm going to talk about your "customers with licences" as developers to try to simplify the writing) Your customer has a customer account with your Jira Service Management…