Trudy P Claspill Community Champion

Hello @Digvijay Singh Gehlot What problem are you trying to solve by making the descendant issues read-only? What would you expect to happen if the Portfolio Epic status changed again to something other than Closed? Is it a requirement that this be accomplished without changing the status of the descendant issues? If not,…

Hello @Eddie Hobart The options to query for linked issues natively are found her: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#linkedWorkItem Unfortunately the functions require you to provide a single explicit issue key for which you want to find the linked issues. So with only native JQL…

Thank you, this option appears off screen and is only visible if the user scrolls all the way to the bottom of the left sidebar. I'd ask that the Atlassian team consider not hiding key features off screen, especially something as simple as this. I'm glad I was able to help you find the option. I encourage you to provide…

I'm glad you were able to find a solution. In my opinion, it would be more efficient and scalable to have a template of the Epic and Tasks that need to be recreated (or the Task and Sub-tasks if you prefer that structure) and use a rule such as described in the posts I referenced. In that way if you have to increase or…

I have not seen any information about the field being deprecated, but I do see, now that you mentioned it, that the field is not listed in the supported fields for JQL documentation. I also did not find anything in the public Atlassian Backlog concerning the lack of support for the field. I advise you to open a support…

Hello @HQRAZAHS I have the capability of changing the project category to 'Software'. Is it the same option you are referred in your last comment "You could consider create a Software project, and moving all the issues to that project. No, that is not what I was referencing. The project Category and the project Type are…

Hello @P Vinod Kumar Thank you for that image, but it does not match the example I showed. In my example I am using the original/old Workflow Editor. It appears that you are using the new workflow editor. Specifically I would like to see the Validator information. In the new Workflow Editor you may see this in a panel on…

I am not aware of a way to change the group to which the "Hidden" option is applied, nor a way to change it only for the Edit screen. There may be a method to do that of which I am unaware. I do not have the time to research if there are third party apps that can help with that.

The manual way: At the point where you want to and the If-ElseIf-ElseIf-Else: Click Add component Click IF: Add a condition Click IF or ELSE: Add condition options Add a Condition Click the Add Component button directly below that IF in the diagram on the left and add an action Click the Add Else button below that. Click…

The More Fields you are showing in that last image is different than the More Fields panel in the issue details view. The one in your last image would be, as it says, for fields you don't use often when creating tickets. It would also be based on the fields available when you are creating tickets, and that list may be…

Hello @VVC Referring to this document: https://confluence.atlassian.com/servicemanagementserver/adding-attributes-to-object-types-1044784524.html ...you can set an attribute to be hidden from users in the assets-users role.

Hello @Anurag Bharati Is there a reason you specifically need to do that within the script? There is a native Clear Field Value post function you could use to clear the field.

Hello @Gaia Sargent With only native functionality it is not possible to create a dashboard gadget that display a 2D Statistics chart of Resolvers and count of issues resolved. You can create a filter to get a list of issues Resolved by a specific user, if "Resolving" an issue can be correlated to the changing of the issue…

Thank you. The next question would be is the user providing any of the information for those fields when they are creating the ticket? Do those fields appear in the screen that the user is filling out to create the ticket?

Hello @Mario Palacios Fernández Can you provide some additional information? The two screens that you showed are what a user would see if they accessed the Project Settings for a project. This is not what a users normally see when trying to access a Service Management project to browse the issues. What are you and the…

Hello @Timothy McKay Can you provide screen images to help illustrate the problem? Are you talking about the "More fields" panel that shows when viewing an issue? Or are you talking about something that the user is not seeing on the screen where they are actually entering the data for the new ticket?

Hello @G P N Welcome to the Atlassian community. At the top of the Community pages you will find the Learning link. This will take you to free, on-demand training provided by Atlassian. You can find Learning Paths under the On-demand learning option You can also use the Browse all learning option to see all courses and…

Hello @gjones Welcome to the Atlassian community. We are a user community using our own instances of Jira. We do not use the same instance as you and have no access to your instance. We cannot provide you with the contact information you are seeking. Do you already have access to the Jira instance, and just need the…

Hello @nathalie_talis A user can be a member of multiple Teams. Given that it would be challenging to have an out of the box feature that could decide which Team to select in such a case. Here is a KB on how to use Automation Rules to accomplish what you want. It references the Assignee, but you could modify it to…

Thank you for that additional information. First, I would recommend having two separate rules; one that rolls up points from subtasks to their parent issue, and one for rolling up points from Stories to their linked Release (issue type). It sounds like maybe you have that already, but I was not sure because I can see you…

Hello @P Vinod Kumar Thank you for the update, Sachin and Trudy. I have implemented a validation process that checks for empty comments whenever a work item changes status. If the comment field is empty, it prompts the developer to "Update Comments." However, despite updating the workflow, the system is not recognizing the…

For a Business project the Columns of the board are tied directly to Status values with each Status value having a column. You cannot rename the columns. You cannot map different statuses to different columns. That is all handled automatically for this type of project. You would have to rename the status, or add/remove…

@PM/이유경 For a Business project the options for board configuration are limited. From Project Settings these are the available options. As you can see, there is not Board option. And these are the only options available from the board view itself. The settings you are thinking of are available only for boards created with…

Thank you for that additional information. Based on the image you provided you are using a Team mananaged business project. With such a project you board configuration options are limited. There is not an option for a "Backlog" screen to which you can relegate the backlog items so that they don't disrupt the focus of the…

Hello @Paras Dua Welcome to the Atlassian community. Given that you have indicated your plan type is Standard, I surmise that you have not modified the Issue Type (Work Item) hierarchy to enable you to have Story issues be children of Release issues. How are you creating the relationship between Stories and Release issues?…

@PM/이유경 Based the image provided the project is a Business project. The Board Settings > Layout > Columns option doesn't exist for such projects.

What about...? Jira Software + Jira Work Management = Jira

No, there is no difference in this functionality based on the license. Can you provide a screen image of what you see?

My curiosity is on fire now wondering how this could be been accomplished! 🔥 

So you're saying not only has the feature been removed but additionally all customization you did previously has been reverted? And you're sure it was possible in Jira Cloud previously. But nobody has any idea how it was done, and there is no evidence that it was ever done? I've been searching the Internet for any…