Nic Brough -Adaptavist- Expert

There is no workaround yet - Team-managed projects don't do linking in a way that the importer can handle yet.

This error is saying what has happened - the card has been deleted, or secured away from you so you can't see it. There's nothing to "solve" here, it's not a Trello issue. If you think the card should be visible to you, you'll need to ask the owner of it to make it visible, or have a conversation with whomever deleted it…

Welcome to the Atlassian Community! In a company-managed project, you set the "Epic Link" field on the story. Team-managed project's import doesn't yet support the import of Epic connection data, from what I can see.

Welcome to the Atlassian Community! Projects in Jira are the issue containers, they determine how the issues within them work. It is not possible to have an issue in two projects at the same time. But projects do not represent teams, they are better aligned with products. Jira Software is built to support more Agile…

Welcome to the Atlassian Community! A board and its backlog (they're two faces of one thing really) are not containers, they are a view of a selection of issues. They're driven by a filter that selects a load of issues (this is often as simple as "project ="), so the first thing to check is if your filter does not…

It does sound like that would work best for you! But you'll want to tell people that moving issues between projects is not part of your process. It does not sound like it should be, if you can do "project = product" (which makes a lot of sense because you can take full advantage of project versions and components) and…

Welcome to the Atlassian Community! Yes, that is correct. Sub-tasks are not really sprint items, they're only seen in the sprint display because their parent story is in the sprint and they are a piece of it.

Welcome to the Atlassian Community! What do you mean by "screen monitoring"?

I don't think the variable "download link" contains what you think it does. You should be using a structured REST call to get the attachment, as documented at https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-attachments/#api-rest-api-3-attachment-content-id-get I can't see how your code would be…

The first lines of the error tell us exactly what the problem is - Jira can't connect to your email server. It's not complaining about not being able to find it, so the name is probably not the problem, but either your network is blocking the connection, or the email server is not configured to let your user in. You'll…

No, look at the last two paragraph in my previous comment. From your release comments, you probably should be thinking about one project per product.

No, that cannot possibly work. Issue type is NOT a field. It's a structural component of an issue. An issue can only be of one type, it's nonsense to say "that issue is a bug and a story", It can only be one or the other. The issue type determines all the configurations of the issue as well, so having two of them would be…

Ok, go to "manage apps" and change the list so it shows all apps, not just user-installed. Does the troubleshooting app appear to be installed and active?

I would avoid the use of sub-tasks for team allocations. Jira Software is mostly intended to support Agile, where it would be the Story that is dealt with by a single team (sub-tasks help the team break up the work that needs doing on the story, maybe for indicating a specific component or technology, or saying which…

Whatever your "pull" is, it should simply be asking Jira for the Status of the issue (most functions in Jira include it in the response by default - when you look at an issue on-screen, it's shown there, when you ask for an Issue over the REST API, it's included unless you deliberately exclude it, the default columns on…

My guess is that you've got 14 issue types in the issue type scheme, and then another 18 sub-task types.

Could you explain the symptoms of "have to reset password"?

You should not be doing mandatory fields with Behaviours. I know it was in there years ago because it was useful, but that was before Adaptavist even got Scriptrunner, and at a time when there was only one way to create or edit issues in the UI. Now you've got lots of ways to do it, Beavhours can't cover them all, and…

>Where did you see the " process entails changing the structure of the issue"? When you said "when we move issues from one project to the next" That's changing the structure of the issue. This is because of what a "project" is in Jira. You've aligned your "team" with "project" which is not a bad thing, but it doesn't work…

It's not a bug. It's a not-obvious consequence of using sub-tasks in Scrum and choosing to drop them from the board, and something I would like tweaked. Technically, the behaviour is correct. For an issue (of any type) to be "done", it should be in the last column of the board. Atlassian should either 1) Change the error…

Can you log in as the user using the REST call, and try to create an issue of the same type that your REST call? Are you offered the affects version field then? Also, if so, is it the first field on the screen (other than summary, issue type and project)? (Basically, we need to check all the things it could be by trying it…

This question is more about what boards are for than your issue data. Boards are not issue containers, there is no such thing as "move from one board to another". A board shows us an issue when the board selects for the issue. There is no way to automate "move issue to another board", because the boards are built off their…

No, not at all. I call them broken when someone has given me enough information about them to see that they are. From what you have said, your process entails changing the structure of the issue you're trying to track (including its human-friendly unique id) when it changes teams. That does not sound right to me. The…

Your projects may well be using different estimates, but they'll be doing it in different fields. My point about the cross-project reporting is about a single field, when projects are using the same estimation field. - you need the field show the data in the same way for the reporting to work.

Of course organisations work in different ways, Jira is built with huge flexibility and power and supports many ways of working. I'm not saying your process is broken because Jira doesn't support it, I'm saying the process is broken because it involves restructuring the entire issue and all the data on it, and moving it…

I'm sorry, but that's complete nonsense. The versions in a project are a set of options you use on issues to indicate what version of a system the issue occurred in and which is (going to be) fixed. A version doesn't contain all your issue data and configuration, like a backup would.

Welcome to the Atlassian Community! 1. Yes,, the issue key is for showing you the unique key of the issue. The issue type field is for seeing the issue type. In a lot of places, it's shown as an icon, so you should be selecting distinctive icons for them, but you can also hover the cursor over it to see the name. I'm…

After you have given it a couple of minutes to get started, what does the log say when you try to visit the site?

Postman does what it says - it sends the request you enter into it to the web site you tell it to contact. Your VBScript does the same. It's ends a message to a web site. I can't tell you how your code might do that, it's up to your code to do it,.

No, that's the opposite of what I said. Could you re-read my answer?