Trudy P Claspill Community Champion

You might also want to make sure that any transition to "not done" statuses include a Post Function to clear the Resolution field. Otherwise any issue that is "reopened" will inappropriately have a Resolution value.

Getting ADO configured "quickly" and appropriately depends a lot on having resources that fully understand your work processes and the configuration capabilities of ADO. Understanding your work processes includes understanding what type of report need to be produced in what format and how those need to be delivered, as…

Hello @Olivier ROBIN You cannot add the Parent field to issue in a Team Managed project. If it is possible for an issue to have a parent, then that will show up here when you are viewing the issue. If the issue already has a Parent, then the ID of that parent will show in the same place.

@Olivier ROBIN (cc: @Dave LIAO ) Please confirm for us the type of project by 1. Go to Projects > View All Projects. 2. Find your project in the list. 3. Show us what it says in the Project Type column. The image in this reply indicates that you are looking at a Company Managed workflow, not a Team Managed workflow. So,…

Hello @April_Delay You need to look in more detail at the explanation for the Issue Linked trigger. It depends on the link that you are creating between AA-1 and BB-1, and the "direction" of the link. Whichever issue in the pair gets the Outward Description of the link relationship is the one that will trigger the rule. If…

Hello @Jean Ann Harrison Yes, this is possible if you are talking about Release that are tracked in Jira. A user can go to the Releases page for a project, select a release version, and open it to see the issues that were included in that release. You can also search for issues in a specific release version by setting…

At a previous employer (in 2021) we switched from Jira to Azure DevOps. There was not a migration path at that time that would support moving all the information for each Jira issue (history and comments as well as some of the core issue info) and no support for moving boards or historic reports. We opted to start over in…

Another possibility would be to create a second board that pulls in only the non-subtask issues and uses Swimlanes set to Queries based on Status. That would show a view of just the stories, though. You would have to click through on the stories to see the individual subtasks.

@Gayle Hutchings Welcome to the Atlassian community! That is correct. A board Column is just a container for mapped issue Statuses. Multiple Statuses can be mapped to a single column. And an issue can appear on multiple boards and be in different columns in each board. Because of this there really is no reasonable way for…

Hello @gordon.varney Thank you for that additional information. In this post, @Bill Sheboy provided an answer that there is an open change request to support setting Rank in the Automation feature, and that there is a REST API that can be used to set Rank. You might be able to create an automation rule that selects all the…

Do you mean you want to automate keeping track of how much time the issue spends in that column? And then be able to report on that later? To do that you could use Automation and 1 or more custom fields. Here is one possible solution: * Create a custom Number field for "Days on Hold" and add that to each issue type where…

Your original post says the requirement is "when a field value is changed in the Epic,". Why are you using a Schedule trigger instead of a Field Change trigger? If the requirement is to do this on a Schedule, I would assume you are including a JQL in your Schedule trigger(s). Please share those details.

@Faruk Erdem I don't have that information. I'm not an Atlassian team member. I'm just another user of their products. You can find product roadmap information here: https://www.atlassian.com/roadmap/cloud?

Forgive me, I misinterpreted the information. That is a Build Key. Do you have your Jira system integrated with a development tool the executes builds? I see in your images that there are two "error" outputs and you are showing info only for the second one. Also they are preceded by a "bulk" action. Can you show us the…

Hello @sprasad Thank you for that additional information. Can you look through the older history entries on HAR-2245 and see if you find one for "This issue is blocked by HAR-2008"? The only way I was able to recreate a situation like this was to (using your Issue IDs in my next statements): 1. In HAR-2008 create a…

Are you working with a Company Managed project or a Team Managed project? That information can be found at the bottom of the navigation pane on the left.

Hello @Janczak Christopher What are "hold column metrics"?

I don't believe that would be correct. Your comparison would be counting all the issues returned by the Lookup, which would be the total count for all Assignees. And as written I don't think it would not send an email to each Assignee. I'll have to think on this one a bit and get back to you. Off the top of my head I don't…

I see in the error message that it is referencing and issue with ID JF-PROD-32097. Are you able to use the Search options to find that issue and view it? Are there any issues from the Kanban board that you can view successfully? Can you view any issues in the JF-PROD project? By default project keys can contain only…

Si los dos proyectos están en la misma instancia, puede usar la función Mover problema para mover problemas de un proyecto a otro. https://support.atlassian.com/jira-software-cloud/docs/move-an-issue/ Esta función se puede usar en un problema a la vez, o se puede usar para varios problemas a la vez. Para usar en un…

"Parent Link" is not the field that Stories use to keep track of their parent Epic. Stories use the Epic Link field to keep track of their parent Epic. You would need to use "Parent Link" in (<key for My Initiative) or "Epic Link" in (<key for My Epic 1>, <key for My Epic 2>) <edit - had to fix a typo which I have bolded…

Can you show us a screen image of what you see? Can you show us a screen image of the Initiative details showing that the Epic(s) are Child Issue of it?

Hi Trudy, I created the filter using basic search to pull in the epics but the filter is not showing the associated stories, so the Plan also does not show the stories. Please show me what you mean by "created the filter using basic search". If you mean you are using this interface: then click on the "Switch to JQL" link…

You would need to get rid of the "If issue matches JQL" component before you can save the Schedule Trigger with the JQL option unchecked. Or you can start from scratch with a brand new rule. Can you try constructing the rule this way and let me know what the results are? Also, please let me know what you have set for the…

Hello @Harshal Kirtane Welcome to the Atlassian community. Unfortunately I have not found a way to retrieve that information. The action of moving the Epic from a Team to a Company Managed project doesn't appear to result in an event being logged in the child issue change log for the unlinking of the parent Epic. 

Hello @Frank Leverenz There is no native function in Jira for that, to show some comments (normal) but not others (restricted). If you don't need to show the comments at all, then you could click on the History or Worklog tabs in the Activity section. Neither of those show the Comments. Alternately ask for an identity that…

That is from a page for viewing Projects, not Boards. The View All Boards page has a URL like this: https://<your Jira Url>/jira/secure/ManageRapidViews.jspa And you get to it by clicking in the menu bar on Boards > View All Boards

When you use a Schedule trigger with a JQL the actions in the rule will be executed for each issue returned by the JQL. You should be able to save the Schedule trigger without a JQL if you uncheck the "Run a JQL" box. I can help you debug the Lookup Issue problem, but you would need to show me the rule after you modified…

Hello @Maroline Johnson Do the watchers of the issue receive notification for other comments on the issue? Have you tried using the Notification Helper to confirm Jira is correctly configured so that a specific Watcher, who has no other relationship to the issue or roles or groups assigned the Issue Commented notification,…

Also note that output will not include issues removed from the sprint.