Nic Brough -Adaptavist- Expert

"Issue" is literally the issue. Most people using Jira would look at it and expect to see the issue key (and they would, although what you see is not quite what it really is) issueFunction is a (sort of) custom field created by ScriptRunner to accumulate a load of issue information together in the index to prevent it…

I tend to use "Issue types are an indication of the most defining kind of information you hold to want to hold about an issue". Not "important", but "defining". This is because the issue type can be used to define how an issue behaves. Think of the difference between using a single issue type of "Pet" and several that are…

Ok, I will copy and paste it for you. You asked: "I want to allow user to choose the Issue type, How I can do that? " I replied: "You do not. Customers do not have access to the underlying issue."

Actually, it is. In Scrum, you do not estimate sub-tasks. You can see hour estimates rolled up if you use them, but estimation by teams is done at the level of the story, not the sub-task. Remember that you're committing to doing the story, not the sub-tasks underneath it, so the measurement should be at that level.…

I have seen one, but it was closed "won't do" years ago.

Yes. You can give the boards the same board filter, so that they have the same view of the issues. Or you could give them different filters (For example, for your bugs, use "Project = XYZ and issuetype = bug" and for the Kanban, and then "Project = XYZ and issuetype != bug" for the developer's Scrum board) Be aware though:…

Confluence doesn't track if something is used or not, unless you install and configure one of the apps that tracks views. I have a feeling there is only one that tracks attachment "view" (I use quotes because preview, view-in-place and download are all tracked as the same thing)

You might struggle with this - boards do not have to match projects, and hence you may have several issues from different categories. You will need to look at each board you want to report on, and use its filter in a dashboard gadget (unless you can pull up some commonality that makes a filter easier)

Could you have a look a couple of comments back?

You can't do this. The backlog and sprints are part of the board. They're the same data. Your scheme would break because data is missing from view.

No. Burndown is defined by "is this done?". If it is done, you burn down. If it is not, you do not. Other states do not matter to this. It would not be a burndown chart if it did (more like a control chart or cumulative flow)

Sub-tasks have the same activity and history tabs as issues.

Yes, admins create the list of possible (global) issue types, and put them in the "issue type scheme" for your projects if you need new ones in your project.

No. Burndown is defined by "is this done?". If it is done, you burn down. If it is not, you do not. Other states do not matter to this. It would not be a burndown chart if it did (more like a control chart)

Yes. But bear in mind production is going to move on, so they will immediately start to drift, unless you are playing back every change to production as it happens.

Cloud Confluence runs on the standard https. So you would be looking at port 443

If the project is a "classic" one, it has an "issue type screen scheme" which tells Jira what screens to use for each issue type across create, edit and view. Find the one you have for create, and you'll be able to edit it and re-arrange the fields.

No, for the reasons given above. If it's any consolation, Atlassian are moving in completely the opposite direction - the market actually wants to derive whether you're part of a project from what work you have. No more people allocating you to things and you needing them to remove you (and them saying no because you…

Could you tell us what you are trying to do? Not how, but what? Problem is you've said "create issue in Jira SR using REST API" - if you have SR, you don't need to use REST, you have direct access to the Jira you are in. But you might also mean you're trying to create issues from somewhere else (in which case, you might…

Not really. If you don't use an identical copy of the source data, then IDs are going to drift off, no matter what tools you use for synchronisation.

You do not. Customers do not have access to the underlying issue. Customers choose the type of request, which you then map on to an issue type - this is a 1:many relationship. Each request type creates issues of only one type. But a type can be created by many different request types)

No need to apologise, we understand! Atlassian support is over at https://support.atlassian.com/contact They will probably ask you much the same though, to see what the differences are. Please feel free to do that here too - we might also be able to help!

Jira and Confluence are separate services with separate permissions. Although most of us do use shared user and group directories, sharing permissions is done on each application separately. It is not uncommon to see things like "member of group X can use project X in Jira and use space X in Confluence", but that is two…

And I should really have answered the question too. Either of your strategies would work, but if you want to do Scrum in any useful way given what it sounds like you are doing at the moment, you will have to use the second one. Stories should be completed in a sprint. (I say Stories, but it's any type of issue at the story…

D'oh! I just realised I tested with a page created before the new editor was added. Yes, the [ won't work on new pages created and edited with the new editor, but exactly as you say in your answer - ctrl-k does.

Hmm. Are you sure it's on Cloud? My Cloud installs all happily go grey and pop a box almost immediately. I'm not aware of a way to turn it off in cloud either.

You manage the request types in the Service Desk Project settings.

No. If you remove the underlying option from a field, it cannot hold that value any more, because it's not there. If you looked in the database, you would see (a much more complex version of) this: Issue has a field. Field contains a value. That value is the key of an option. If you want to see the option, you look up its…

That means your confluence is not correctly configured to connect to your email service, or your email service is not running.

Yes, if you are willing to code for it - you'll need to write a "plugin" that provides them. I believe you can do some board templating in them, but I'm not sure (I know you can define a workflow though, which will feed into the board) There's even a getting-started tutorial -…