Petter Gonçalves Atlassian Team

Hello Jennifer, The new issue view is still a lab feature on JIRA, so our developers are still working to implement new functionalities to it - It still not in the production version. That been said, the rank field was not configured to be displayed in the new issue view yet, but we are already working to implement it. To…

Hello Sandra, Welcome to Atlassian community. By default, the Remaining estimate field (verbleibende zeit geschätzt) is automatically configured with the same value as the Original Estimate when you set it and then updated based on the work logged in the issue. The scenario above doesn't match only when you manually set a…

Hello Rebecca, By default, the time tracking estimation of JIRA considers a working day as 8 hours. That been said, I think it is considering the time you have configured as 3 working days instead of a whole day. Can you confirm if that's the case? To check how your time tracking is configured, navigate to JIRA Settings >…

Hello Trisha, I believe you are talking about the complete column of a board in your project, is that correct? Could you please let us know what kind of project you are using (Business or Software)? A Software project board (Scrum or Kanban) can be easily customized on Board settings > Columns (Unless you are using a…

Hello Christoph, Can you please let us know what is the version you are currently using? Indeed, a bug was opened about this behavior for versions before 7.0, however, it should already be solved from version after 7.0. Additionally, I believe that if you right-click the attachment and select the option Print it would…

Hello Sigga, Welcome to Atlassian Community! Please, check the documentation below to know how you can get all the work logs from issues using REST API: - Get Issue Worklogs Once it is exported, you can filter in an external application by the started and Updated parameter which time range is relevant to you. Let me know…

Hello Toby, Thank you for raising this question. Can you confirm that you have Site-admin rights on both JIRA and Slack? Also, can you confirm which is the add-on that you used to integrate JIRA and Slack? The most used add-ons are: - JIRA Cloud for Slack Official - This is the official integration provided by Atlassian.…

Hello Oleg, You could use a date and time custom field to receive the current time when your issue is assigned, however, to trigger this action when an issue is assigned, you would need a plugin. I would use Automation for JIRA and configure the following rule: P.S: In my case, I used the Due Date to execute the rule, but…

Hello Chegg, There are three levels that could block users to access issues on JIRA: - Product Access - Project Permissions - Security Levels Since the users are not able to even access projects, it can only be caused by the Project Permissions or Product Accesses. Please, check the following: Product Access: - Navigate to…

Hello, Welcome to Atlassian Community! Unfortunately, JIRA does not have a feature that would calculate the difference between two date fields, however, there are some options that you can use to achieve that matter: 1 - You can export both resolved date and Due date to CSV (Excel) and calculate it. 2 - You can use the…

That's ok, Christos. We will be waiting for your answer.

You are welcome, Lee! In order to include all issues with a specific label to a board, you just need not perform the following steps: - Navigate to your board > Click on the three dots icon > Board Settings > General > Click to Edit filter query - Add the label to the query: Labels = "XYZ" Please, let me know if you have…

Hello Paula, Thank you for contacting the community about this question. Indeed, I'm sure there are several other users facing the same questions as you due to the complexity of this feature. There we go: 1 - Do you have to be using a Scrum board? and Sprints? In fact, the Epic Burndown Report is optimized for scrum teams…

Hello Suhas, Unfortunately, there is no such functionality to achieve this matter on JIRA natively, however, you can use some plugins to accomplish that. My recommendation would be to use Automation for JIRA and configure a simple rule with the Smart value {{issue.epic.watchers}} to copy the Watchers field from the Epic in…

Hello Christos, Searching for similar errors, It seems that you probably have a null user in the userbase table, external_entities table, or the XML backup. Please, try the steps in this documentation to properly troubleshoot the problem and fix it. Basically, one of the following queries should return the problematic null…

Hello Tom, Thank you for your feedback. The sub-task issue type is the the next feature to be implemented on Next-gen project, however, our developers have not informed a fixed date to implement it, as you can see in the Next-gen roadmap documentation. You can track their progress on the implementation in the suggestion…

Hello Manikanta, You can a Filter results Gadget to each issue filters you would like to return. For the reports you are asking, here are Filters: 1 - Create JQL filter: Component = XYZ 2 - Create JQL Filter: Release = XYZ 3 - Create JQL Filter: "Issue type" in (Story, bug) and status = Accepted and Created <= XYZ and…

Hello Lee, In fact, you will need to have any field with a determined value to match the criteria in the JQL query of the board. That's the only way to share the epic with multiple projects. You could use even a custom field to accomplish that, like a select list, for exemple. I suggested the Labels field because it's…

Hello Ian, Analyzing your request, most of your requirement can be returned using the filter results, except total hours/hours to date (progress bar) %, however, you could display this same information as fields using the time tracking (Original Estimate, Remaining Estimate, Worklog). Additionally, if you want a more…

You are welcome, Joe! Have a nice day.

I'm glad to know you were able to solve your issue, Andrey. Have a nice day!

Hello Yuliia, Welcome to Atlassian Community. Analyzing the screenshot you provided, it seems that you are using the New Issue View of JIRA. As you can see in the bug reported below, the new issue view is not able to render Wiki Markup yet: - Wiki Markup does not work in the New Jira Issue View Please, feel free to watch…

Hello Kyle, Unfortunately, The inbuilt JQL functionality of JIRA does not have a parameter to search for issues where their linked Epics matches certain criteria, however, there are a few plugins that you can use to achieve it. I would recommend you to use the Scripted JQL Functions provided by ScriptRunner plugin. The…

Hello Lee, Analyzing the scenario you provided, I think that you can use labels to share the Epic across multiple projects, naming the labels with the related board to better identify in a fast view which boards it is added to. For more information about this field, check the documentation below: Use Labels to organize…

Hello Daniel, Welcome to Atlassian community. JIRA SD does not have the correct triggers to automatically update a field value based on another, however, you can use Automation for JIRA plugin to achieve it. You just would need to configure a simple rule like the one below. P.S: I used the fields department (Select list -…

Hello Hannah, Could you please provide us a screenshot of where you are trying to search and the results you are getting? Trying on my instance, I was not able to reproduce the problem in the default search bar of Help Desk: Once you provide us the steps to reproduce it, we can report it as a bug on the official Atlassian…

Hello Joe, You are correct. The general "Manage Sprint" permission will always be applied to the JQL Query behind the board's project, considering ALL the issues returned by the query and the cloned ones. The root cause of this behavior is that the cloned issues inherit the Sprint value from the "parent" issue in the…

Hello Priya, Can you please provide us a screenshot displaying the page you used to configure the field on your request type? I would like to better understand what do you mean by adding a default field. When you add a field to a request type using the conventional method (see screenshot below), it is placed only for that…

Hello Dibya, Welcome to Atlassian Community! You can achieve this functionality by using Bulk operation: - Navigate to JIRA > Click on search > View all issues - Type the following query: "Epic link" = "XYZ-123" Where "XYZ-123" is the issue key of the Epic linked to your stories - Click on the three dots icon > Bulk Change…

Thank you for your answer, Jeroen. In fact, JIRA Service Desk features should be migrated all together with the project if you have already subscribed for SD in the target instance. You only must manually add the customers once the import is complete. Please, let me know if you have any other questions.