Nic Brough -Adaptavist- Expert

OK, that's ruled out the tech side of it. Now we need to look at why your people are trying to comment on issues that they do not have the issue key for. Why do they not know what the issue keys are? Or why are they clicking "reply" and then removing the issue key from the subject?

Could you explain what this has to do with Atlassian stuff?

There's nothing to fix on the Atlassian side, your database needs to be set up correctly.

Welcome to the Atlassian Community! There is no "Jira Confluence", do you mean just Confluence? Software development is better supported by Jira Software (Jira Service Management is basically help-desk, Software gives you Scrum and Kanban boards to help track development issues) So if you're doing Software development, I'd…

Welcome to the Atlassian Community! Issues are separate items from each other. Deleting one issue has no effect on another, except when two issues are parent/child or are linked together, in which case the link will disappear from the remaining issue because there's nothing to link to any more.

Welcome to the Atlassian Community! You don't get to disable this on Cloud. (It would actually stop some things working in Confluence, so you wouldn't want to do it anyway)

Two things here: 1. Can you check that you are using a "create or comment" handler, and not just a "create" handler? 2. Why are your users removing the issue key from the subject of the emails when they "reply"? Why are they trying to email your Jira about an issue that they don't know the key for?

Oops, looks like someone got a field mapping incorrect in the migration! Anyway, no, I'm sorry, but there's no bulk actions for editing or deleting options in fields that are list-based. You'll have to delete each one manually.

Welcome to the Atlassian Community! How are you currently defining "responsibility" in Confluence? You can always grant rights to people for a page by making sure they are granted the various permissions in the space the page is in (space settings -> permissions)

The export is giving you the raw stored data, unadjusted by your time zone settings. The -11:30 hours implies you have set your time zone to the edge of China or New Zealand.

Yes, it is possible to "integrate". We can't tell you any more than that without a definition of what you mean by "integrate"

Get rid of the forced variable types (the "as" bits). The whole point of "def" is that it decides what the type of the variable is. 

The report should be reporting on the data you have. There is a very important point in your question here: "what happened in a closed sprint if changing the story later changes the closed sprint?" Why are you changing the data in a closed sprint? The sprint is done, your open issues have moved on, your closed ones should…

I am not sure what the question is, I am sorry. The confluence-administrators group is in the global permission for administrating Confluence because you need a group of administrators to do the admin work. You can't remove it because you should not have any need to stop being able to admininstrate your system. Could you…

Please see https://community.atlassian.com/t5/Feedback-Forum-articles/Atlassian-stands-with-Ukraine/ba-p/1961059 

I do not think there is anything that you can do about this with technology. Github, Gitlab, git itself, Bitbucket and all the other software can't go out scanning the entire internet for illegal uploads of your code. Not without massive processing power and incredibly fast networks. I'm afraid if you have engaged with…

I'm sorry, I use "script or automation" quite a lot. I work for an Atlassian partner who sell the biggest scripting app for Jira in the marketplace, but I try not to advertise when I'm answering questions - it might be the right app, but it might not, and I'd rather not sell stuff when it's not right. Anyway, it's not…

Ahh, ok! I was stuck on how you'd done it, but if you haven't, that makes sense! So there's a bit of an essay here, and some uncertainty, but please bear with me. Starting with your help centre screenshot, the process that appears to happen for raising a new item is: * User selects one of the three options, and fills in a…

Ok, that's the components and component leads in the project, but how are you tying each "area" to a particular component?

Ok, so don't use team-managed projects. Company managed projects have supported the Epic link field on issue create for years. Edit - I am sorry, the last couple of comments were probably too short and very terse and did not do a good job of explaining the earlier conversation. As discussed at length, short version is: *…

How are you "creating each area as a component"?

Welcome to the Atlassian Community! Edit the workflow, and change the "create" transition so that it ends in "refinement" rather than "to do"

Why? There's a request for team-managed projects to have Epic Link fields already.

It makes perfect sense when you understand what a board is for and that the last column is "done" FWIW, it's just the right column because a board is there to show the team what they are currently working on, or have finished with recently or in the current sprint. Once something is done, the team doesn't care what the…

The built-in watchers field is not really handled as a field in Jira, it's more of a function. You can't get to it directly as though it were a field, you have to use add/remove in its own interface, not the field view. There are a couple of apps that provide a field-like interface on to it in the marketplace, which you…

> As Jira is not supporting a sprint level adjustment of velocity based on available capacity It's not supposed to, you're not supposed to be adjusting velocity, it's a number that comes out of your historical data. Story points are not supposed to be used for capacity either. Your velocity based on Story points is there…

Welcome to the Atlassian Community! It sounds like your sub-tasks are using a different workflow, one that either doesn't have a transition from in-progress to done, or if it does, one with a condition that is blocking you from it.

I suspect your workflow has a "workflow property" set on the "closed" status that says "no one can edit this issue". It's not an uncommon one to see, especially when people base their workflow on the Jira default one. I would want to check that with an admin (they'll need to edit the workflow to see it), but if it is true,…

How have you created these "groups" and what do your people put into a new issue that determines which group it should be part of?

Admins can also jump directly to a list of boards from <your base url>/jira/boards