Petter Gonçalves Atlassian Team

You are welcome, Patricia. Since the description field is appearing correctly in the old issue view, I believe the misconfiguration must be in the project settings > Issue Layout of the project. Please, ask your project administrator to also check this functionality. Let us know what did he find with this investigation. :)

Hello Ivan, Thank you for your explanation. Now I understand that the parameter you would like to change in the bulk operation is the linked type and linked issues of the ones returned in the JQL query. Unfortunately, JIRA does not have this kind of functionality in the bulk operation feature. We have a feature request…

You are welcome, David. Please, feel free to open a feature request for the functionality you are looking for in JIRA: https://jira.atlassian.com Let us know if still have anything else we can help with.

Hello @Natalia Lezhai , You can create a select custom field with all the request type groups where the customer can select in the ticket creation page. Additionally, if you use a different workflow for each issue type and have different request types on each group, you can use a post function to automatically set the…

Hello Jamesson, Sorry for the late reply. Please, let me know if the explanation below helps you to better understand how you can set approvals to log work in JIRA: Basically, it is not possible to set approvals to allow/restrict the log work on JIRA directly. The approval feature can only be configured to block/allow the…

You are welcome, Asad. Have a nice week ahead. :)

You are welcome, Rosa! Have a nice week ahead. :)

Hello Anthony, I understand that you would like to reset the SLA when the issue priority is changed instead of just adjust the SLA that was already counting when the priority was different. Have I understood it properly? If I understood your request, you can achieve your need by performing the steps below: - Create a new…

Hello Khalil, Welcome to Atlassian community! The query you mentioned has worked just fine in my personal JIRA Cloud instance, so I believe that maybe the username you added in the query has changed on your JIRA site. Can you please confirm if the user you are adding in the query is still using the same username/e-mail in…

Hello Tarek, Since the new issue view is still a lab feature, our developers are still working to implement some of the functionalities available in the old UI, including the comment restrictions. For the specific matter you mentioned, you can check the progress of our development team in the feature request below:…

Hello Patricia, Welcome to Atlassian Community! By default, the description field should be displayed in the new issue view of JIRA. I suggest you check the following: - Click on your profile picture at the bottom left corner of JIRA Application > Personal settings > Turn off the new issue view and check if the description…

Hello Maria, Welcome to Atlassian community! You can properly copy any field from parent issues when creating sub-tasks by using the post function Copy value from Other field. These would be the steps: - Navigate to your project > Project Settings > Workflows > Click to edit in the workflow assigned to your sub-tasks - On…

Hello Douglas, I believe you should be facing a problem with next-gen reindex, where the issues are not considered resolved since they were not moved to the last column, but only kept in one and it was configured as the last column. That been said, I suggest the following: - create a new column in the "In progress"…

You are welcome, Tom. Have a nice weekend.

Hello Vivien, Please, vote and watch the suggestions provided to increase its priority and also receive notifications about any updates. As soon as we got any ETA or updates from the Dev team, they will absolutely add it in the mentioned suggestions.

You are welcome, Jack. Have a nice weekend!

Hello Rosa, Thank you for the provided details and the workaround you used. After digging a little bit further and performing some tests with the new information you provided, I realize that when you add the user to the Approvers of the issue, the user is treated as a customer for the purposes of notifications. That been…

Hello Prasad, The ability to sum-up story points from sub-tasks to Stories and from Stories to Epics is something that cannot be achieved at this moment using only JIRA, however, a high number of users have requested this feature, so our developers are considering to implement it in the future. Also, as a big number of…

Hello Esther, Thank you for the detailed description of the problem you are facing. Indeed, the behavior described by you where the selected fields are not remembered when creating the issue through the board planning section (backlog) is a known bug in JIRA application. Here's the link of the reported bug: - Create Epic…

Hello Boris, Welcome to Atlassian community! Since the new issue view is still a lab feature, our developers are still working to implement some of the functionalities available in the old UI, including the sum-up of sub-task estimation to its parents. For the specific matter you mentioned, you can check the progress of…

Hello Doug, As you may know, JIRA Service Desk customers are configured with a different set of notifications, since they have limited access to the ticket fields and content. That been said, you can perform the following steps to properly configure your customer notifications to return fields like to summary and…

Hello Asad, Welcome to Atlassian community! The only way to restrict issues from appearing in a JIRA board would be by configuring the board filter in a way it does not return the mentioned issue. That being said, you must add a field to differentiate both epics created in each board, like labels or a select list custom…

Hello Joshua, The steps to add a custom filter to return issues of a business project would be by: - Click on the search button at the left bar of JIRA Application > Advanced search for issues: - Configure the filter you want > Save it with the name you prefer - To switch between your created filters, you can click in on…

Hello Pavan, Welcome to Atlassian Community! I believe you talking about the "Fix version" field in JIRA issues, is it correct? The "Unknown" value in the version field means that no versions are selected for it in previous versions of JIRA Cloud and Server. Now, the same value has been updated to "None" and can be…

You are welcome, Manish. Let us know if you still have any other questions.

Hello Offer, Thank you for your answer. Can you tell us if the user Tomer Zilber (tomerEmail@gmail.com) is the only customer appearing in the field? Also, can you confirm in the User management page or in the Audit Log if the user once had access but is deactivated now? I think you can possible been facing the behavior…

I'm glad to know my answer has helped you, Colleen. Have a nice day!

Hello Jack, The actual behavior you mentioned where attachments are being automatically downloaded when accessing JIRA is not configurable in JIRA Application. Basically, it does not exist in the application settings. That been said, I really believe this problem is being caused by an external source like a plugin or…

Hello Rosa, The "conflict" you mentioned will not cause the user to don't receive notifications, but there are some other points that could cause it. Please, check the steps below for further troubleshooting: 1 - If there are any security levels in the issue, make sure the user is added to the security level 2 - Check if…

Hello Chana, Unfortunately, the only fields available to be displayed in the Issue Calendar Gadget is the name and Key of the issues, together with the date you selected. We have a feature request created to implement more fields to be displayed in the gadget: - Ability to Display Multiple Field Values - JIRA Issue…