Nic Brough -Adaptavist- Expert

I suspect you're not seeing a lot of traction because Kanban already has estimation built into it...

You'll need to find something that can transition the issues through your workflow until it reaches the right column. I think I need to question why you're doing this though - your columns are supposed to help you represent your process, but you've given them names that do not sound like they are a process. Is this really…

How do you know that "they are not going out", rather than "not arriving" or "being ignored (spam filter)"? Have you run an outgoing email test to confirm you can get a basic email given your current sending setup?

Only if you have some form of SSO enabled for your website that is shared with Jira as well.

Welcome to the community. I'm afraid this is not possible yet, there's no way to swap a project between Classic and Next-gen. Best you can do is create a new project and move the issues you want into it.

The columns on the board gather together issues in a particular status (or set of status), so to get an issue put into a coliumn, you need to transition it to one of the status in the target column.

The burndown chart does not look at dates. It looks at the issues that were/are in the sprint.

Do you have an account manager? If not, then you'll need to raise a support request at https://support.atlassian.com/contact I would question "want to run SQL" - you almost certainly do not. The Jira database is the worst possible way to get information out of Jira, and should only be looked at as a very last resort. Plus,…

There is no way to do that easily or directly by issue type, but it can be done with some setup and a bit of education for group B. I'll try to give the most simple structure for it here. * Set up the project so that Group A and B all have Browse, Create and Edit rights. * Create two workflows (probably get the easy one…

Ack, sorry, not quite the right answer, Community Villa is not supposed to be seeing the issue, so you don't want to include them in the security. However, the principle about where the security level applies is the same. You have two things in the permissions analysis - first Community Villa is not in the security level,…

No trials are available for Jira server any more. This is because it's going away in a couple of years, and you can't buy new licences for it.

The screen definition is simply what fields are presented to a user when they take a particular action (create, edit, view, or transition) It does not matter whether you have "level" on the screen or not. For this issue, someone has set a level, I'd guess at a time when level was available on screen, or it may have been…

You will need to install one of the scripting apps to do this, or use Automation for it (which won't do it with a script)

The isssue you are looking at has a "security level" set on it. Community Villa is not named in the level as someone who has access to the issue. It's not a bug, you've just hidden the issue from them with issue security. Either change the security level on the issue to one that does include the user, or amend the security…

I am stuck on what you mean by "appendix", I think there's something lost in translation? Appendix usually means (in writing terms) - a chapter of the book or document that is not part of the main story but is added to the end for additional reading or information. In Jira terms, I am not sure how that translates. Could it…

Most people log "hours in the past", and need to, because they often finish a task and then log it later. That said, yes, you don't want people going back and amending logs after you've started reporting off their logs and your processes say they need logs in at a reasonable time, so it's perfectly reasonable to ask for…

There's no "copy board settings" yet, so I'm afraid you'll ave to do it manually, adding the columns you need in the new board and mapping the status from there into them as appropriate.

Just as a quick addition - some apps do have functions that enable them to be have no effect on a space, or be partially or totally enabled. It's most notable on apps like the Comala or Scroll ones, where you've got spaces where you want workflows and controls on content publishing (so you use the apps) and then internal…

Eh? "For Jira, the id of the user creating the Jira issue is initially put into the Reporter field for that new issue. " is the same as "Reporter defaults to current user," So it used to be true.

I'm going to have to go with a blatant advert for Adaptavist stuff - https://pc.adaptavist.com/ should be worth a look for you. Yes, we're going to charge for it (I think) in the long run, but it is free for now. I would like you to try it out, if nothing else to give us feedback on what it can and cannot do - the more…

It used to be true in older versions of Jira, up until the creator field was added as a separate record. The reporter has always been changeable (if you have the permission), with the intention to allow "report on behalf of". Reporter defaults to current user, but you can change it. The creator field was asked for because…

We can't help you with this, you have not told us what you have done, what the rest of the errors are, what is in the logs, or what you are trying to do. You will need to give us a description of the problem in full before we can do anything. All we can tell you from here is "please read the logs, they should tell you why…

This sounds like some form of script or app trying to do some form of sanity check when you create the page. I'm afraid Confluence doesn't create pages like that itself, you'll need to track down what app is doing it and reconfigure it.

If you were to get rid of the error messages, your users would not know why they can't do what they're trying to do. That would be a very counter-productive and annoying thing to do to them. You can get rid of them in one way - configure the system so that your people can use it properly.

Restore defaults does not restore the previous set, it takes it back to Jira's off-the-shelf defaults are. I'm afraid all you can do is re-add the columns you want from scratch

Your licence must have ended before 7.6 was released. You do not need to downgrade, you can still renew existing licences, up until 2nd Feb 2024. An upgraded licence would allow you to use 7.6

I understand that you think you want this, but you don't want the security nightmare it creates. That's why Atlassian are saying "no", because it's throwing all the security out of the window.

I think you might want to expand on that?

It will be. When the resolution field is put in front of the user, it gets set, there's no way to leave it blank. So if it's on create or edit screens, anyone creating or editing the issue will resolve it!

Your excluded stories don't go anywhere or change in any way. A board is a view of a selection of issues, and all "excluding" them does is means they don't appear on that board. You won't be able to get to them from that board, but you can carry on using them everywhere else. Or re-include them so they do appear.