Nic Brough -Adaptavist- Expert

You'll need to use the url/web-link option in the links, or remote-issue links (if you've set up application links) not issue-links.

Oh, excellent, I didn't know we'd implemented the events in there (there's 500 of us now, I can't keep up with everything every team is doing!) It looks to me like you've got everything set up right in there for sending email (that's common to all events, so not new!). Mail templates look fine to me, and leaving the…

Unfortunately, there's a weakness in Jira that means you can't mix and match like that - you'll find once you've created a context by type or project, you can't create other contexts. This is because you could do something like "project = ABC" for context 1, then "issue type = bug" for context 2, and you could create a…

Welcome to the the Community! Jira's user names and logins are not indexed in a way that would support that, so it can't be done. It's not common for use names to have any discernable pattern like "starting with x", so Atlassian have never worried about doing it. I'm afraid you'll either have to name your individuals, or…

Ah, ok, well, this is a bit obscure but you can still do it. You'll need to read up on *exactly* which version you should take for your version of Jira (Core) and then go to the rather well-hidden "download the .obr" list over at https://marketplace.atlassian.com/apps/1213632/jira-service-management/version-history .obr…

That display is telling you what both "project types" are, and are not going to be renamed, as they're accurate. There's two things people talk about as "project type", with two or three options. * A project is always company-managed or team-managed * A project is always from one of* Jira Core/Jira work management (a…

There's no way to do this the way you are suggesting. The word "issue" that you're seeing is, as you say, not an issue type, but actually part of the UI. On server, you can actually change it, by writing your own "language pack" and get people to select that as their own language, but that isn't project related, it will…

Welcome to the Community! 8.13 is a "long term support" version, it will receive updates and patches for a lot longer than other releases and is a good target for you at the moment. I suspect there will be one more long term release of Jira Server before all support ends for it on the 2nd February 2024, but I do not want…

Ah, hang on, why are you putting urls into the link field? Issue links are done by issue key in the Jira you are already in. As you've used two different urls in the screenshots, I'm going to guess that you're trying to link to other Jira systems. Issue links fields do not support that, they only link to things they know…

No, but yes-ish. No, you're not missing anything, you can only create issues in a single status in a workflow. If you need an issue to be in another status, you have to create it, then transition it. The workflows behind the projects and issues can logically only have one start point - it's not quite as simple as this, but…

Welcome to the Community! We are just that, a Community of people here to talk Atlassian. We're not support or pre-sales. We might be able to help you with this, but we'd need you to describe where you are stuck here in the question. For support from Atlassian's Trello team, ask at https://trello.com/contact#/ but be aware…

Changing the name of fields or adding and removing them is something your administrators have to do. You'll need to ask them what they have done to your Moscow custom field.

No, you'll need to use one of the apps that can create more layers of hierarchy

Welcome to the Community! The backlog is a list of issues that need attention. By definition, completed stories do not need any attention, they're finished, so they will not appear in a backlog. You can still search for issues, dig out their sprints and all activity and so-on, but as a completed issue is done, it won't…

You've answered your own question here - " I only pressed edit and update" - you edited the issue and changed the field during the edit. If you did not change the field yourself, then it may be that a listener heard "issue updated" and amended the field for you.

Welcome to the community! Some reports have a link that will take you to the JQL they are using, but for a lot of them, we have to infer them. The sprint report is quite simple - it's based on simply "sprint = x"

No, Jira doesn't track component renames beyond a line in the audit log, so there's nothing that would be able to trigger an email (no "event" is fired)

I am sorry, I know this is frustrating, but it is all I can tell you. It's just as frustrating for me, because I can't think of any other way to get this message. The error message you are getting is happening because you don't have permission to link the target issue to the current one. Or there is an app interfering. I…

There's no single place you can get a list of advanced functions because a lot of them are added by different apps (and hence vendors) Componentmatch and versionmatch come from Scriptrunner ( https://docs.adaptavist.com/es/latest/functions/match-functions ) but other advanced functions are built into Jira (…

You'll need to remove the epic-link field from the create and edit screen for this type of issue in this project.

To do this calculation, your code will need to fetch the issues in the sprint and read the data from them to work it all out. The Greenhopper api you've found is a deprecated old version of the REST API from before Atlassian renamed it Agile and then Software.

The message in red in your screenshot is coming from a validator on the create issue process. I suspect that validator is failing your attempt to create the issue.

No, burn-down is only done when an issue becomes done. That's the last column on the board in Jira software.

This wouldn't really be a velocity report if you could do it - velocity is reported for a team and is done off the board the team use. If you've got multiple boards, you're no longer reporting on team velocity. Anyway, you can do it - define a search that includes all the issues that the four boards include individually,…

I'm afraid repeating the unclear sentences do not explain them. * As Alex already covered, yes, you can create custom fields and use bulk-edit to update them. To do it, you search for issues and then use the "bulk edit" function from the search results. * Could you explain your second question a bit more? * And what are…

Yes, that's perfectly clear, but Walter has already said what you should be doing - Select Create a kanban board, base it on an existing saved filter or project and assign it the same source as your scrum board. That should create your kanban board and have it display the same data as on your scrum board.

Again, Jira is not trapping any information about when you've "read" an issue update, so there's no way to do this.

What is the error message when they try to log in?

Nope, you have to export one at a time.

I'm not sure you'll find anyone here who has a lot of knowledge on performing downgrades like that. It might be better to ask in an Azure forum?