Nic Brough -Adaptavist- Expert

It's the same answer as the last time you asked. See https://community.atlassian.com/t5/Jira-Software-questions/quot-Not-able-to-decide-Release-type-Please-check-fixversion-or/qaq-p/2062427

Welcome to the Atlassian Community! Crowd has some audit tables, the main ones being cwd_audit_log_changeset, cwd_audit_log_entry and cwd_audit_log_entity, which you can join together for a big flat table of all audited changes. But it won't be as useful as you think it might be - Crowd doesn't record that much detail.…

Welcome to the Atlassian Community! What phone number?

I see the problem, it's a natural way to work when you're a small close-knit team, especially if you're co-located Growth forces more rigour - I tell stories about Adaptavist's growing pains - when I started, I was the 27th-ish employee and when I picked up a piece of work, I could mutter "I'll get ABC-123" so the people…

I am not sure what you mean by "clocks" here. Do you mean you want to look at the times between changes of fields? Like "This issue was unassigned when created, Alice was assigned to it 4 hours later, and kept it until Bob took over 3 days later"? There are some functions for "time in status" built in, and more if you take…

Welcome to the Atlassian Community! This is not one we can really answer for you. The "validation" you need to do is something you need to define, not the application. What is your "validation" if you're going to be working in the healthcare industry? (and also, where - software requirements for healthcare in the UK are…

I think the problem here is that you don't have a process that makes it clear who is working on something, which you can't fix in software.

There's no way to do that. The problem here is that you didn't have a velocity in those closed sprints because you didn't estimate and start the sprint with any knowledge of what you had committed to. The charts are actually accurate already, you can't change the history.

Ok, you can secure individual issues with issue security schemes 

Jira is not a documentation tool, it's an issue tracker, there's no reason to tell people that someone else is looking at, or has it open in "edit" mode (especially as there's loads of different ways to "edit" an issue). If you're editing an issue, that's fine, you save your changes. The fact someone else might be looking…

It uses whatever filter you tell it to when you configure the report before running it. You won't be able to change it to look at severity or anything else. The report is intended to tell us how long things are taking to get resolved. Running it against severity would be nonsense.

Welcome to the Atlassian Community! You can't do this with labels, they are derived from issues that have been labelled, not a select-list. You can't easily import a list of options into a select list, but there is a cheat - if you list them all out in a spreadsheet, with one line per option, and two columns (summary and…

Welcome to the Atlassian Community! No, you can't ungroup the date/time fields from the date/time panel in the issue view.

Could you show us the sub-task that should be feeding up to the parent in the screenshot?

No, you must not modify the database directly, it will, quite simply, break your system. You shouldn't even be looking at the database frankly. What problem are you actually trying to solve? And why are you looking at the database?

What do you mean "improve the detail and presentation"?

I'd question what your security team is saying - what is the logic behind blocking the access? What security problem would it solve? Given that the users can do anything in the UI already, it's not going to plug any security holes. There's still no reason to block your users using the API. They're using it for some of the…

You've not set up your mail send correctly - Jira is trying to log into your email server as a certain user and the email server either does not know them, is not configured to let them send mail, or you're using the wrong connection credentials.

There isn't one. There's many different ways to view a Jira issue, and you wouldn't want to trigger change when people view an issue. It's the other way around - you should be automating "set assignee" or some other "person has got this" flag when an issue is moved from open to in-progress.

Ok, server means you'll need to talk to the administrators of the service and the machine(s) it is running on. The descriptions of the slowness you've given us strongly suggest a non-performant server. That's not actually Jira or its config directly in most cases, but that the server doesn't have the resources to run Jira…

Welcome to the Atlassian Community! Templates, like pages, are not based on others. Your copies of the global template are independent of it, so if you change the global template, the other templates will not be affected. A template is not a structural thing, it is, well, a template, as in the dictionary definition. A…

Could you read the previous answer please?

Welcome to the Atlassian Community! This is what it says it is, you already added the key, but with a different user name (you should not do that, keys are not supposed to be shared between users). You'll need to identify which account you shared it with and either use that account for access, or remove the key for the…

You can't hide the standard filters from people. But do you mean you actually want to hide issues from people?

Welcome to the Atlassian Community! This is something you need to do in your Atlassian site maintenance, we can't help you here in the community. If you do not have site admin rights, then you'll need to contact Atlassian support - go to https://support.atlassian.com/contact and create a new support request, selecting…

It's not possible to do this. JQL simply returns a list of issues that match, it has nothing to say about how they are displayed.

Ok, so there's nothing wrong there, except that the fix version is not on screen. You should be able to add it, and then set it to match the parent issue, then the board filter will kick in. (Not sure why it's not directly inherited, but get the setup fixed first)

There's a couple of places to watch. https://www.atlassian.com/roadmap/cloud is for seeing what is coming up. Bear in mind that there are no "planned releases" in the sense that "new version will be deployed on date X" - Atlassian start rolling out new changes when they're ready to go out, not on a fixed timetable, and it…

Jira doesn't actually care if someone looks at an issue (and it can be hard to define "looking" - open directly in the issue view, sure, but what if the issue appears in a search in the issue navigator, or on a board, or in a roadmap? All places where someone could be "using" it and jump off to change it) Basically, you'll…

Hmm. Ok, so "issue updated" will happen on every edit of any issue, irrespective of type, so the next question is to look at who is not getting notified. Is there anyone who does get notified of edits on sub-tasks? The people who should be getting notified are getting them for edits of story level issues? They can…