Comments
-
Hello @Jim Welcome to the Atlassian community. Natively Jira does not have a JQL feature to enable you to retrieve children of multiple Epics unless you want to explicitly list the Epic issue keys. There are third party apps that provide additional JQL functionality that would enable you do retrieve children of Epics where…
-
Hello @djx Welcome to the Atlassian community! In this example Themes (Initiatives) are the top level. Features (New Feature) are children of Themes. Epics are children of Features. When adding "children" you can't skip levels. Epics can be children only of Features. Standard issues types can be children only of Epics. I'm…
-
Good catch, @Bill Sheboy ! @Richard Williams In the 2D gadget the Epics with the same totals (assuming the totals per Epic actually agree in the two gadgets) seem to be ordered alphabetically by Epic Name. Take a look at the issue keys for the underlying Epics. In the Issue Statistics gadget, are Epics with the same totals…
-
Hello @Ben Finn Currently there is no flag in the API equivalent to the Shared Configuration option in the UI. There's a change request for that here: https://jira.atlassian.com/browse/JRACLOUD-45929 Looking at the API it appears to have parameters for all the schemes that would be associated to a Company Managed project.…
-
Team Managed projects is a newer functionality set than Company Managed projects. You may notice that there is different functionality available in the boards for a variety of elements for each of these project types. The functionality is not currently in lock step. I can't speak to Atlassian's design decisions regarding…
-
Try looking under Products and selecting the site to see if you can access User Management at the site level. To access it from Directory I believe you would have to be an Organization Admin.
-
Hello @Martin Remove the curly braces that you have around the explicit issue key in the JSON.
-
Hello @Stephan Lewis If you are using an Edit action to copy the data there is an option under More Options to turn on/off emails based on those changes.
-
Hello @vinod palan Welcome to the Atlassian community. The Clone feature does not clone comments. This page provides a bit of information about what is copied during the Clone. https://support.atlassian.com/jira-software-cloud/docs/clone-an-issue/ If you want to also clone comments, that might be able to be done through an…
-
Hello @Paul Wiggers How are you getting the data that tells you the number of issues resolved per user per day? When do you think the agent should get credit for the issue being resolved, based on the statuses you specified?
-
Hola, Es posible que los cambios se hayan realizado a través de Reglas de Automatización u otra funcionalidad automatizada que se activó indirectamente por una acción realizada por el usuario. Puede ver si se activaron reglas de automatización para un problema o si se tomaron medidas al respecto haciendo clic en el campo…
-
This post appears to be a continuation of an earlier thread: https://community.atlassian.com/t5/Jira-Software-questions/Resolving-Jira-Sprint-Burndown-Chart-Issues-Investigating/qaq-p/2347072 I encourage responders to put their responses on the original thread.
-
Actually you can have projects with the same name, as long as they have different keys.
-
I believe this change requests relates to your scenario: https://jira.atlassian.com/browse/JSWCLOUD-12539 Column width adjusts automatically based on the browser window size, trying to include all columns in the windows but making them no less than a minimum width. If all columns can't be displayed at that minimum width…
-
Can you provide a screen image of what you see when you simply are typing in the filter name?
-
What is the Rule restricted to projects setting in the Branch for your Comment propagation rule? In Rule Details who is specified as the Actor for the rule? Does that actor have permissions in the JSM project? For an instance where the Comment propagation rule was triggered but found no issues : 1. Can you show us the…
-
Hello @Maham Nadeem Welcome to the Atlassian community! This is the JSON that you need: { "update":{ "Multiple assignees":[ { "add":{ "id":"{{changelog.assignee.from}}" } } ] } }
-
Hello @Autumn Justice I think you are talking about the Release button that appears in the upper right corner above your Kanban board. Is that correct? Can you share with us the Filter Query used by the board? Does the user have the right permissions for all Projects that are within scope for that filter?
-
Hello @Aditya Rajaraman Welcome to the community. If you look at the For/Related Issue/JQL, you might notice this field that restricts further actions to being performed on the issues from the JQL that match the specified project. If your rule is triggered by a comment being added to issues in Project 1, but you want to…
-
Hello @Louise Woods What is your evidence that the rule is not working correctly? What does the Audit Log show for the rule execution?
-
Have you checked the Estimation Statistic setting for your board? What is it set to?
-
Hello @Hitesh Is your rule getting triggered? Can you show us a screen image of the rule itself and the details of the Edit action? Can you show us the Audit Log for the rule execution? Can you show us an example of an issue that has that custom Date/Time field?
-
"Should be" is not the same as "are". :-) If the totals are not the same can you provide an example showing one such Epic and its list of child issues?
-
Happy to help. If your question has been answered and your problem solved, please consider marking the Answer as Accepted to help other users find posts with validated solutions.
-
Hello @Richard Williams Do the Totals per Epic in the Two Dimensional chart match the Totals per Epic in the Issue Statistics chart? The configurations for both say they are sorting by Total, but we can't see the totals in the 2D chart.
-
That is a different macro than the macro in the image I posted. For the macro you are using you need to simply start typing in the name of the filter or project you want to use, and the screen will show you potential matches from your linked Jira instance. The select the one you want.
-
You said "I checked the rule in Project 1 " You need to check the rule in Project 2 - the rule you showed us that is trying to transition the issue to a new status. Is the Transition rule being triggered at all when the Clone rule creates the issue?
-
How exactly is that not working? Provide examples of the dates used in each step and the results.
-
You're welcome. If my replies solves your issue, please consider marking the Answer as Accepted to help other users find posts with validated solutions.
-
{{createdIssue}} is an object just like {{issue}}. You can access the same attributes in both. If the Assignee field has been set during the Clone step, then you can reference that field with {{createdIssue.assignee}}. You don't need to use a branch to do that. I'm unclear what problem you would be trying to solve by using…