Nic Brough -Adaptavist- Expert

Ok, thanks, that's the "add new section". I can't see any reason why it would be adding extraneous text, unless you've got a bug or a very strange tweak to your Confluence that is adding it Can you tell us what version of Confluence this is (from the ? menu top right) and maybe ask your admins what customisations they may…

You would usually use "definition of done" at the sprint level only. Acceptance criteria on a story is a bit more fuzzy. Some people will use it as the same as "definition of done for this story", others might be looking at it from a more testing angle, telling them what needs to be tested and what the results should be,…

So, some thoughts: "it tells the issue if it's an issue-level, sub-task, or epic-level - yes and no; there is only 1 issue type that works as epic and it is predefined. I can choose between Task(Level) and SubTask when creating an issue type." So yes, and it is very important to understand that those three groups work…

I am sorry, I was not clear. I meant the duplicates needed to be created as sub-tasks, from within their intended parent issues, but it's great to hear that the "move" worked for you (it's a recent addition I think - last time I tried to convert in Next-gen, there was no option to do that!)

I am sorry, but you're wrong. A backlog is a part of a board, which is a shared view, controlled and configured by the board owners. If I am not the board admin, I cannot control the abitrary fields. And that is correct because it is supposed to be a shared view with everyone looking at the same think. In the issue…

Jira has no way to do this natively, and hence you'll need apps to do something like it. The closest I have have used is Idalko's Table Grid, but I would check the marketplace for others that may be better for you rather than go on one recommendation.

Hi Nora, welcome to the community. I do not think you have misunderstood anything, but I think Jira is not clear on explaining the way it works for some things. Sub-tasks are always part of their parent, they cannot exist outside the context of their parent. I think when you say "search for existing issues", you are using…

The user directory settings are totally separate from the application links in each application. In your Jira, you've done the right thing and updated the user server, but you do not mention telling Confluence that the user server (user directory) it is using has moved. As an admin, go to admin -> user directories, find…

Atlassian broadly have three types of support None - you can only ask questions here in the community. This is for free and the $10 (starter) tiers of the software Standard - you can raise support requests via https://support.atlassian.com/contact - for anyone with any tier above the $10 licence Premium - you can still ask…

I can't generate licences, I'm not the account owner. Plus, there's no "Test licence" for Atlassian stuff. Your production licence includes a "development" licence option though - go to your my.atlassian.com account, find your licence and look at the links beneath the key, one of them is for a developer licence.

Gadgets (for server) can be written as apps by anyone who wants them, so yes. I'd check the marketplace for gadgets that might help first though.

No. The point of software as a service is that you don't have access to the underlying servers, it's managed for you.

@Rodney Hughes- they've shut down the first one as "won't do", with a long explanation. Second one is still "gathering interest" (For what it's worth, I voted - I'd like to be able to see more info from the padlock)

I accepted on your behalf. There should be a green box just above each answer to a question (in this case, there is only one answer). It should be showing either as a frame with "accept this answer" or a solid "answer accepted" box. The community support and developers would be interested in why you couldn't see it - did…

I don't know that function in Trello, sorry. I'll move this into the Trello collection so that other readers are aware of what system you are using without having to read all of this thread.

I think you need to go into the field configuration for the project and issue type, and find the field description, edit it, and remove the javascript. Javascript in field descriptions is an old and clumsy hack that is being removed from Jira

I do not know if it will solve it. It is the next step in trying to fix the problem. I'm worried that you are doing this on a production system though, it is something you should be debugging in test.

There's no way to do that.

How was the field being made mandatory? Specifically, was it via the field configuration or by a validator in the workflow?

No, there's been no change.

No change yet.

No, I'd like the issue navigator to stay single line. What I'm saying is that the backlog and issue navigator are there for two different reasons. The UI for the navigator works for searching and looking through issues, and should be single line, and I have control over what fields I choose to have there. I don't want to…

Apologies for the delay. I am looking through unanswered questions for ones I might help with, even if they're a bit old. The data gathered for database monitoring is held in momeory while the application is running, and then reported on when requested. If an orderly shut-down is requested, I think some of it is written to…

It might do, but there's not enough information in your screen shots to tell us. The question is if you are in the same "screen scheme" in each screenshot. If they are separate screen-schemes, you are fine. If they are the same screen-scheme, then yes, you will be replacing what "create" uses.

The issue navigator and backlog have differing amounts of space either side, and if you look over 99% of people's issue navigators, you'll see them scrollling left and right because there is not enough width for all the fields they have on the screen. Doing that in the backlog would make it even worse - having the fields…

I think you could use these two to do it: The first script shows you how to get a value from a field so it can be replicated into the same field on to a sub-task when the sub-task is created. The important part of this is to look at how a value is handled in variables. When you look at a version field, you will find its…

I think you are missing the point. The issue type determines how an issue works. The issue type tells the issue what values are valid for fields, it tells the issue what fields are available and on what screens, it tells the issue if it's an issue-level, sub-task, or epic-level (and more layers provided by apps and…

You can only run Jira on one single URL, so this will not work, even if you get the proxy right.

No, that's not possible - the comments are not attachable to versions either. Remember that Confluence is not a document (or code) repository. It's light on functions around tracking objects because it's not expected to do it.

A high number itself, no. The number is limited by the database, but to extremely lrge numbers. I've seen a 95% functional Jira project with over a million issues in it. The failing 5% were reports attempting to read too many issues at once.