Nic Brough -Adaptavist- Expert

Welcome to the Community! There's a two-part answer here. First, you can get most of the way there by: * Search for all the issues you are interested in, and save it as a filter * Go to a dashboard and add a 2-dimensional filter gadget. Configure it to * use your saved filter * select Sprint for the X axis * select…

Welcome to the Community! Um, yes, that's fine, but there's no question in your statement. Nor any information on what you are doing or what you are trying to achieve. What do you want to connect with Sourcetree?

I suspect this question needs to go to your admins, not the Community here! If you were on Cloud, then the answer would be "Cloud changes regularly, so yes, there have been changes recently. But the nature of those changes would not suddenly make a field mandatory without warning, Atlassian would have been yelling about it…

Are all your "done" issues (and their sub-tasks if they have any) in the last column on the board? That's the only thing that matters when you close a sprint. Any issue not in the last column is considered to be incomplete, irrespective of status and resolution.

I'm not sure where you are stuck now - you've got the "copy from" in the ... menu, so add that to your rule, and add the component you want to add as well. The explanation as to why you do it this way: A multi-select field like components contains a list of options (0, 1 or many). If you use just set "component to X", then…

I'm afraid not - that's down to the way Jira Cloud works, not SR. I know we're getting places with getting Atlassian Cloud to enable SR to be more clever, but I don't know where we are with UI changes like that.

What do you mean by "Bug burndown"? Burndown charts measure delivery vs commitment in a sprint, they don't have anything to do with bugs directly.

Does it not appear when you click the menu elipsis ... to the right of the field, where all the dynamic options are?

Ok, but that still applies. Project import imports issues into an existing project. It does not create a project.

Ah, the error message is telling us what is wrong, but unless you've seen it before, you probably can't work it out from there. The logs would tell you more, but even then, take you on quite a roundabout route to what the problem probably is. I mean if you go chasing the logs, you'll probably find (after three or four…

There is no recommendation beyond "don't do sub-tasks of sub-tasks". In most cases, they are a huge over-complexity, leading to attempts at micro-management and have no real use. Instead, question the "need" for them. You will almost certainly find out that you don't need them at all. Or, in the case where you do, you are…

Yes, Atlassian did it twice. Many many years ago, they added an import that enabled administrators to import lists of issues. his one has to be limited to administrators because it allows us to import cross-project, broken data, and configuration data (options on custom fields, new users, etc). Later, project import was…

Welcome to the Atlassian Community! Could you please explain what this has to do with an Atlassian application?

Ah, yes, icons from emails, annoying things which I'd prefer to dump as well. (Just because they look ugly) If your emails are coming into a JWM or Software project, they will be being processed by a Jira email handler - you may want to look into using a different one, as a couple of them can do things like stripping…

It's not something created by Jira developers, it's something you have got set up in your system. A dashboard is a customisable and shareable reporting place, which can have all sorts of displays and reports on it, but these are all chosen by the person who creates the shared dashboard (the default system one has to be…

I am a bit confused by the question - Listeners do not have a front-end UI, so there are no tabs in them. Do you mean somewhere else? Like an issue screen? If so, then @Vero Rivas answer is what you need.

It doesn't work with team-managed projects yet. Atlassian is planning to implement it, but I don't know a time-line (If you "create new plan from a project", it lists only my Company Managed projects)

It's not quite like that. You're not far off, but I think of it a little differently to this. A Jira project of any type is a collection of issues and configurations for how they work. A JSD project sits on top of a project and provides functions such as the portal, queues, SLAs, requests, the email channel, and the…

Welcome to the Community! We have no way of knowing. We know less about your Jira than you do. It's certainly not a standard Jira-speak term, so I suggest you ask the people who are using it or set it up (you haven't told us what it is - project key, acronym, name of a project, something people are typing into text fields,…

I want to live in The Culture. Or Ankh-Morpork.

I am sorry, but you did not get the point. I am not sure how else to explain that The 1153 you are quoting is not the sprint id. Could you have another read of what I wrote?

You create two workflows that link to those status on the different steps. In those two, obviously To Do and In progress are pointing to shared status, but the other "ready for" status are new individual ones.

Yep, most of us just live with Epic and use them as Features because of the renaming things. The UI elements are indeed components and labels, but they're all hard-coded. Epics do get closed, when all their stories are complete.

Not off the shelf, it only does Issue -> Sub-task. Jira Software adds Epics, so you can do Epic -> Issue -> sub-task. Advanced Roadmaps allows you to add layers over Epic (Initiatives and themes for example) Until very recently, that was it, the hierarchy was just those, and it wasn't codified. You can also rename Epic to…

A TLDR version of that: Issue -> Sub-task relationship is done with sub-task code Epic -> Issue relationships are done with the "Epic Link" field (In fact, in the database, they are also issue link types, but they are not accessed by us users as issue links) So, the question is, are you trying to * Create issues under…

What functionality don't you have? Your automation's "action" section doesn't contain an Edit issue function at all? Or you don't get offered something when adding an edit action?

Status are shared objects - your workflow does not contain any status, it has pointers to the global list of status. When you edit a status, you're editing that shared object, so everywhere it is used gets changed. You will need to add a new step to your workflow, creating a new separate status for it. That will be…

Welcome to the Community! You'll need to talk to the users of that Jira (possibly the admins?). We here have less knowledge of, and access to, that system than you do. I think you have clicked on "help with Jira" instead of "help with the thing Jira is doing tracking for"

Yep, exactly that - conditions do what you need, you don't need Scriptrunner to do it. Although, you might consider writing the condition with Scriptrunner ;-) Much as I love SR, don't use it for things Jira can already do - always use native functionality first!

Scriptrunner, so I did not have to write entire plugins to do clever post-functions, conditions or automations. I should point out that I don't think it existed (outside Jamie's head) when I started working with Atlassian stuff. (I say "stuff", but it was just Jira - Confluence was released 2-3 months after I started…