Nic Brough -Adaptavist- Expert

Be careful not to add resolution to the create or edit screens. If you do that, then issues will be created already finished, or if you only add it to edit, then they will be resolved as soon as someone edits anything. Only use it on transition screens. Remember that if you resolve an issue, Jira considers it complete,…

Ok, as far as I know, there's nothing in Confluence that will read the project timeline data directly. You would need to find or write an app to do that (I am not aware of any, but I think you could do it with Scriptrunner) The best you can do with native Confluence is replicate the timeline on a page, using the Jira…

Welcome to the Atlassian Community! You need admin access if you want to administrate the app or its presence in Confluence, yes. But to see any functions or features it has injected into Confluence, it depends entirely on the app. It may be using information (like permissions) to hide itself, so it only appears when…

Hi Leonardo, You have added some global custom fields, and put them in the default project configuration schemes. This will make company-managed projects take them up if you use the shared schemes for them. But you're looking at a team-managed project. These do not use schemes for their configuration; all their…

Welcome to the Atlassian Community! Where are you storing these Jira dates and what are they representing?

Hi Kerrie, There's no way to do this. Jira has no way of knowing what you intend to do with an issue next. It can only do "move to done" because done is an absolute decision to finish the issue.

wttc @[deleted] I'm afraid this is broadly incorrect as an answer to the question. The flaws are: The first step in creating a hierarchy is to, well, create the hierarchy. Not creating a project. When you create (or update) a project, it will start using the hierarchy you have defined. In both team and company managed…

Welcome to the Atlassian Community! Could you explain further? Confluence does not use "new" for creating new content, and PKG and MPPS are not Confluence terms. Are you using an app installed into Confluence to provide these things? If so, which is it?

Ok, that is what I thought - "status in team test" is reading every issue, and even though the result is only 136 issues, the board is not going to cope with everything. Limiting it by project, or category by project reduces the context down to a size the board believes it can cope with.

Welcome to the Atlassian Community! What exactly are the symptoms of "nothing works for creating spaces"? What do you get on-screen when trying to create a space, and what are the errors in the logs?

Welcome to the Atlassian Community! No, there's no way to do this. A lot of stuff admins do needs them to have global access, and they could not do the role without it. You can permission your HR projects so that your admins can not see them in the UI - admin rights mean "can do admin", not "can see or do anything", but an…

Welcome to the Atlassian Community! No, there's no way to lengthen the summary. It is supposed to be a summary, not a description, and if it were longer, you'd have people complaining that it's getting truncated in their emails and reports.

Welcome to the Atlassian Community! You will need to be on a Premium subscription to do this natively. Jira only has two layers at the core - the story level and sub-tasks. Jira Software adds Epics above story. Premium has "Advanced Roadmaps" that enable you to create more layers above Epic. So if you have that, you can: *…

For CMPs, once you have added the field to the shared create and edit issue screens, it will appear when you create or edit. You don't need to do anything else. For TMPs, you will have added it when you were setting up the project's issues, which again, then makes it available on create and edit.

Could you show us the configuration? The names shown in your sheet are not the names I would expect to see in the mapping.

As I said in my answer, status is a global object, not local to your workflow. It's a convenience to be able to create new status while editing a workflow, but it is not done in the workflow. When you create a new status in the workflow, it gets added to the global list. But if you remove a status from a workflow, it does…

That's not Jira admin, it's site admin. You need to configure this in Jira.

Welcome to the Atlassian Community! Technically, the resolution field is not "mandatory" because it can, and should, be left empty until the issue is resolved. What is actually happening is that your people cannot select "empty" ("none") from the resolution list when the issue is in a create, edit, or transition screen.…

Ok, I think we need to see your full query (the working one with the project clause)

You can use the parent-status scripted field in * displayed on the card, so you can see that while the issue is in "to do" itself, it's parent is "in progress" for example * quick filters * for the card colours * swimlane definitions I usually use it in quick filters or on the card, I usually have other uses for swimlanes…

Welcome to the Atlassian Community! No, the service uses a standard set of fonts and sizes, and there's no way to change these.

Ok, so you're seeing 136 issues when running that in the issue navigator, but a dying board when that filter is selected for the board filter? (Not swimlane/colour/kanban-done/quickfilter, just the board's core filter)

Welcome to the Atlassian Community! Almost certainly not. It's not how Atlassian recruit, and although there is a boring essay on how they do it at varying levels, it's not worth it. There is a simple test - ask the person to give you the link to the job posting. Atlassian now post almost all roles online (the exceptions…

Welcome to the Atlassian Community! The page ids you are seeing here are essential to the way Confluence works, there is no way to stop them changing, other than to prevent all editing and child-page creation. You are going to need to look to other data to do what you need. Would a page property work?

I would like to see a lot more of the screen, I can't see where you are working.

Hi Salih, To add to what Trudy said, there is a big problem with Scriptrunner migrations, although the cause is actually that Server/DC and Cloud are simply very very different products. Scriptrunner sits on top of the Atlassian applications, and hence is also two very different products. With a lot of stuff that cannot be…

Welcome to the Atlassian Community! Yes, you already found it - don't include a "projects in (x, y, z)" clause. This will select all projects, and I suspect that's why you are hitting "too many issues", it is looking at all the issues in the system. You might want to give us your search so we can explain it more (obscuring…

Welcome to the Atlassian Community! You will need to give us more information. What are you trying to rename, and where? A screenshot of a name tells us nothing.

Welcome to the Atlassian Community! You'll have to give us more than that. What were you doing, where were you in the interface, and what was all of the error message? What happens if you try again?

Welcome to the Atlassian Community! There are two types of project you can create in Cloud - Company-managed and Team-managed. In both cases, you need your new field to have a "global" context, so that it is available to all projects and issue types. Your new field will be included in Company-managed projects…