Comments
-
You'll need to go via https://support.atlassian.com/contact
-
It's perfectly possible to do this, it's something Jira has done since version 2. As an admin, go to Admin -> Issues -> Issue Type Schemes. These schemes tell Jira what issue types to use in a project, drawing on the global list of issue types. For you, it sounds like you need two schemes - NOC with Incidents and Requests…
-
Yes, when I say "Jira", I do mean "Jira Core" - that's the platform you need to run Service Desk on. I'm not sure how you think this is going to help you with a "licence crunch" - you're still going to need the same numbers of licences if you separate the systems,
-
I think your company needs to catch up on security. You need to stop using compromised protocols like EWS.
-
JSD is not, nor ever will be, an "independent application". It is an application that you install into a Jira Core. You can run it separately from your existing Jira, but to that, you will need to install Jira + JSD somewhere away from your Jira.
-
No, there is no way to give the gadgets different titles. Their names are generated by the code in them.
-
You don't. The permission to change an issue is controlled by the "edit" permission in the project permission scheme. There is no field level control - you can either edit the issue or not.
-
Go to the page you want to create a child of. Click "create". The default place for the new page is under the page you were looking at.
-
No, the file won't be there by default, you need to create it for yourself.
-
No, the components belong to their projects and are separate and distinct from the components in other projects.
-
No. You need to script/code this, which means writing an App, or using an existing one.
-
Start at https://developer.atlassian.com/server/jira/platform/rest-apis/
-
Ok, could you tell us what the actual error messages are?
-
Set the space permissions so that both X and Y can see the space. Then restrict pages A and B to "group X only", then move page A2 so that it is under page C which has no restrictions.
-
No, as that would destroy the auditable information about who really created it.
-
You need to give it a valid url
-
There's nothing else I can tell you - if you are an admin (which you are if you created the board), then you have "board settings" as the first option in the ... menu at the top right. For "classic" boards. If you create a next-gen project/board then there are no settings and hence no option. What do you have in the ...…
-
If you created it, then you are an admin of it. Given that, then ff there is no "configure" option for it, as in your screen-shot, then it is not a Software Kanban board, it is a board that comes with a "Next Gen" project, which do not have configuration options.
-
No, the view screen is not configurable to that extent (although I'd question why you want a decent issue tracker to take on the look and behaviour of legacy system)
-
You are missing the permission to see the issue. You need to add yourself to the project, so that you match the criteria for the "browse project" permissions the project has.
-
You do not need to have the same add-ons, but the import will drop the settings from the add-ons if you don't have them in the target system.
-
If you are on server, there's a cog icon next to your profile icon near the top right. If you are on Cloud, there should be a "project settings" link in the mid-to-left side bar.
-
You might be a system admin, but you're not an admin of that board. These are different things. Ask the admins of that board to add you as an admin.
-
Try another browser - does that have the same problem?
-
Go to the project, go for the admin section, and select the field options.
-
Ok, so you need to ask the admins of that board to add you as an admin.
-
Admin gives you admin rights. Not project rights. My thought is that you (temporarily) should add yourself to the project.
-
What do you mean by "reassign"? Confluence pages are created by someone, and edited by that someone and possibly others. It has no real concept of "page is 'assigned' to someone". So I'm a bit lost on what an assign person might mean.
-
They already have, since version 4 - it's the label field
-
Go to the project and tell it to use the new copied configuration. Then change the configuration so that it makes the field optional.