Nic Brough -Adaptavist- Expert

Welcome to the Atlassian Community! I'm afraid we, the community, can not do that. These are things that should be being defined within your teams and organisation, and we're not in your teams.

Have you tried the tests given already?

Welcome to the Atlassian Community! This is exactly what it says it is - the account you are using for the connection does not have "create issue" permission in the project you are trying to create the issue in. There's two possibilities in your case usually - first that you are logging in as someone who has admin rights,…

It sounds to me that your "tasks" are a type of sub-task. The rest of what I'm going to say is based on that assumption, so don't bother reading further if that assumption is wrong, just correct me! Sub-tasks are a fragment of their parent story, they are not an issue in their own right. For that reason, they are not…

This is an annoying one, but something that makes sense if you look at it from the point of view of the people who are given a story to implement in Jira, without fully understanding the wider picture. Listeners work off events, and "issue updated" events are only fired by changes to issues. When they are, the event…

Great, but why did your admins remove it?

Welcome to the Atlassian Community! This usually (but not always) means that the issue is not in the current or next planned sprint (when there is no active sprint), but has been in a sprint in the past, or has been added to a far-future sprint.

You can't really do this with Kanban. Kanban does not care about issue levels - your backlog is a stream of cards, and each one is an item that needs doing. It does not care whether they are Epics, Initiatives, Themes, Issues, or Sub-tasks - a card is a card. If you're going for a Kanban approach, you have to work out how…

I'm also a scrum master, and I can tell you that every course I've been on, the original and all the refreshers, were very clear that sub-tasks (as implemented in Jira and most other scrum tools) are not sprint items. I've worked in all sorts of places that try to do scrum-like patterns, ones well outside just software or…

I am sorry, I forgot to say - I don't think you have done anything wrong here, I think you might have just run into an odd case where the data in your target system is not ready to accept data from your source, because JPD has not done all of its initial setup in the target yet. Nothing we could have predicted or avoided!

Welcome to the Atlassian Community! What, exactly, are the symptoms of "can't assign"? Can't find their names by starting to type them? Assign issue link vanished? Error message when trying to commit a change? The usual problem here is a change of permissions that means you're not allowed to assign any more, but we can't…

Surely "How I learned to stop worrying and love the bom silence"? I know what you did there, it's one of my favourite films. It's such an eye-opener to do this. You get so much of your life back, and it can even rekindle your interest in work. Taking the time off, deliberately not looking at work, can make it a lot more…

Ok, I think we need a screenshot of a sample issue. By that, I mean we should identify an issue that you think should be showing on the sprint, but does not. So a search for something like "project = XYZ, and sprint = 123 and Status = done" (for the board you gave us the config for in your screenshot in response to Marta…

Welcome to the Atlassian Community! This is broadly what it says it is. Your account does not have any access to this system, beyond a search for help. You should probably ask the people who asked you to use it for access.

Ah, yes, I'm sorry, I did not quite understand where you were looking. I'm afraid that box is limited (to an arbitrary 50 because it's a round number to humans who tend to use decimal) to prevent performance issues. The only way to get to your result is to put in more of the search to narrow it down more, so that it falls…

Welcome to the Atlassian Community! The short answer is; The space importer will not import a space with the same key as an existing one. Your import will fall over at the first hurdle! That's of no use to you, of course, other than the basic "don't kill what I've got already" protection. You do have some options, but…

The way Atlassian will tell you to do that is * Correct your workflow (as per my answer) so that it sets and clears resolution at the right time * Use bulk-edit to re-open all the issues * Use bulk-edit to close all the issues again, going through the "ask for resolution" screen, or the post-function you added in step 1.…

Do the transitions into the end status (rejected, done and done-done) all have a transition screen with the resolution on it OR a post-function that sets the resolution automatically?

There's nothing wrong with the issue navigator. When you enter "status = ...", it does not go off to read what issues might have a status, it just looks at the list of status you have in the global list. If you want rid of a status, go to Admin -> Issues -> Status and look at the list. Ones that are not used in any…

No, you will need to generate your own evaluation.

Ok, that would mean that your ToDo app is broken.

You will probably need to ask your administrators why they removed it.

Ah, ok, that means you are using a simple board which does not have a filter setting. You can assume the filter behind the scenes is "Project = XYZ". Which puts us in a place where you don't actually have any "done" issues to be shown on the board, according to your screenshot! Could you try a search for "project = XYZ and…

That suggests you have tried out Jira Product Discovery on the free site, but not on the target site, or that the target site has not yet had the new permissions for JPD added (I seem to remember that they only started to roll out a week or so ago, so some sites may be behind). I would try creating a JPD project in the…

It's working fine for us. That error message usually means your server can't reach the marketplace, suggesting a networking problem with your server.

Check the "general" tab in the board configuration (from the options menu near the top right of the board - the ... menu)

What is the board's filter? Could it be excluding the done issues?

Um, issues that are done should not appear in the backlog. The backlog is your list of issues to be done. If they are disappearing from your board when you mark them done in the active sprint, then you probably have not mapped the done status to the right column.

If you don't have any numbers and the next page > at the bottom right of the issue navigator, then the query is returning fewer than 50 issues and you don't need to use next page.

Welcome to the Atlassian Community! That looks like gajira-cli is not including the base URL of the target Jira system in its REST calls. Have you configured it with the right base URL?