Bastian Stehmann Community Champion

Hi, If they are the same, Jira should not recreate them. Are there any errors/messages in your import-Log? You can map them manually if you tick the checkbox for manual mapping.

Hi, Beside linking to an issue you can also add "normal" links, eg to web pages. This should also work for links to documents on an SharePoint server. If you want to share an email, I think it will be best to save that email as file and save it as attachment. If only the attachment are important, add only those.

Hi @Tracy Blomqvist, if you add an column for issue type to your CSV File, you should get that as option on the Mapping-Page while importing. Then you can select Issue Type from the Dropdown and the IssueType will be mapped.

Can you try to send a Post-Request to .../auth/1/session and post the response you get here.

Hi, yes, Groups is one way, Project Roles is the other one. You can grant both of them permission to create issues. Project Roles are far easier to manage, as they can be managed by Project Admins, whereas Groups can be only managed by Jira System Admins.

Ok, as far as I know you can not have one username for two userkeys, so you will have to change the usernames before migration, so that the "new" user-data and "old" user-data will both be connected to the same username. I would do that directly within the database (Backup Database before) if I must do that. There it is…

Hi @Abinash Satapathy, did you also set a resolution to that issues. As long as the resolution is unresolved, Jira will handle the issues not as closed.

That's right. In Jira you can have this hierachy: Epic - Story - Subtask That's all that comes with Jira by default, if you want to add more hierarchy-levels, you will need an addon that brings that availability. Just been looking in the marketplace, maybe this may help you:…

Thanks for that explanation, that makes it clearer. One more question, do you have the same users in both instances (meaning person X has login x.y@company.com in one instance and x.y in the other instance) or are the users distinct and you are only adding new users while migration? If you only add users, it will be…

Hi Stephen, it depends on the kind of project you created, which issue types are included by default. If you want to have also an Feature issue-type, you will have to add it as Issue- Type and then add it to your Issue Type Scheme. To do this, you must have jira administration permission. Go to System-Setting (the cog-item…

You are right, that tables are not updated because they must not be updated. What you see, is the userkey, and that stays the same even if you change the username. That's the trick with keys in databases... If you want to change the userkey (the id that is referenced everywhere), I see two ways to do that, but both are…

Hi Jesper, just noticed that you wrote in the summary that it is a status, Probably the best way is to add a new column "On Hold" to your sprint board in the board configuration and move the "on hold" status to that column. Then all issues with that status will appear in that column.

Hi Jesper, how did you mark your issues as "on hold"? Is it a status? A custom field? Something else?

I often used postman to test calls to the api and it works fine. Did you add the authorisation to your api-calls? It should be also in Headers-Section then.

Hi, Kanban Backlogs were just introduced to Jira, so this is probably an error, as this query will work for Scrum Backlogs (issues should be added to a sprint if they are not in the backlog) but not for Kanban Boards. If you just replace the "sprint is empty"-part with "status=YOUR-BACKLOG-STATUS" you should get what you…

Hi, the Activity Stream respects the permissions. That means, if you have project, where Finance and IT will discuss the sensitive informationen, only the users that are allowed to view this issues/comment/... (have the Browse Project permission/are in the right security level/...) will see this in their Activity Streams,…

Hi, can you clarify, what mappings are not updated? We rename users often via UI or REST-API and never had problems with this. Maybe this explanation helps to make it a bit more clear how Jira works. Jira has to different attributes for users, the username and the userkey. The username is used for login or if you type in a…

Hi @Santy Nelson, just go to Enablement Academy(link is in the partnerportal) and then choose Learning Path from the menu. Then you see the accredidations and start the sales and technical sales accredidation. There is no extra preparation for this learning paths, you just watch the videos and answer questions related to…

Maybe adding a new status to your workflow like "further investigation" or something like that will help. You can then exclude issues in that status from your KPI.

Hi @Shana, yes, thats right. When we use the second strategy, everthingy is left in the production instance, because we do not have found an quick and easy way to get the data back. We change the permissions to switch on and off visibilty of the projects, so it is just one click to make it possible to search some issues…

First, make sure the scrum master does have a jira account, so that he can access jira at all. Then, go to project settings > Users and Roles and add the scrum master there to an Role. Make sure to add him to a role, that is able to edit a issue. To check, which roles have which permissions, go to Permissions in project…

The Scrum Master must have an jira account and need the right permissions in the permission scheme used in the project.

We are discussing this topic often with our customers, because we did not find the one, best solution yet. Our customers are often facing the problem, that they want to do some housekeeping to keep their Jira instance clear but they must keep records for several years. In most cases we use one of the following ways. If the…

Maybe this idea is a possible workaround for you. Instead of closing the incident, leave it open and add comments via post-function to this incident whenever a problem to this incident is added or transitioned. That way you must not make the problem itself available to the customer portal and the customer can see progress…

Thank your for explanation. I think, that you should try my suggested solution anyway. Let me try to explain why. With a Quickfilter, you define a JQL that selects the issues, that should still be shown on the board. So in your case, it should select all issues with labels (except automation) and all issues without a…

As we can not know, which screens you use in what projects/issue types/workflow transitions, we can not advise you, which screens you should select. You can check in the Screen Scheme and Issue Type Screen Scheme that is used in your project, what Screens are used for which Issue-Types. To find out, what screens are used…

You have to add an or-clause for the issues without label: labels != OutOfScope or labels is empty

Hey Sune, great to see it works now.

Hi @Sune Hinz, if I remember correctly, you just have to make sure to have the Story Point field enabled for the custom issue type and have the Estimation method on the scrum board set to Story Points.

Thanks for that hint, I always forget that...