Walter Buggenhout Community Champion

Ok, thanks for adding that information @shreya bhatt What I can see from the screenshots and the tags you added to the question - not being familiar with your site - you have a Jira Software project, but clearly a site that was set up for Jira Service Management. Could it be that you / your organisation started a trial of…

Hi @shreya bhatt, Do you have a license / product access to Jira Software? I see near the top right that you are very obviously using Jira Service Management, but to see boards, ... and related features of a Software project, you do need a license to Jira Software. Hope this helps! 

It just sorts the list of results, @b_hafez. it does not bring any additional issues in or out the list of results and it does not matter in what order you send out the reminders. So - nothing wrong with it, but it doesn't add any value. The more you add to the query, the harder it becomes to read. And on that note: I just…

Hi @b_hafez and welcome to the Community! since this is to trigger an automation rule, I would personally leave out the ORDER BY updated DESC part at the end, but I don't see anything wrong with your JQL. Hope this helps!

Hi @Tobias Koch, For migration issues regarding apps, it is best to contact the app vendor directly. I have noticed that the documentation page you linked yourself does have a direct link to contact support. Hope this helps! 

Hi @Farid Hadj-Hamou and welcome to the Community! You can't change that anymore. But, so what? We all make mistakes. The story has been added to the sprint and removed again because it accidentally slipped in. I suppose it did not impact the team's work in any way and you know why the gap is there, right? So, just explain…

Hi @Glenn Andreas and welcome to the Community! The standard hierarchy in Jira is: Epic -- > Standard issues types (Story, Bug, Task, ...) -- -- > Sub-Task issue types These (bottom) levels are fixed and - as of today - can't be changed. So, out of the box, adding a task below a story won't work, nor does inserting a…

While I can get my head around certain use cases with a kanban board, I cannot understand why you would want to apply this to a scrum board. The whole idea behind scrum is that you prioritise items in a (product) backlog and - very consciously - have a process in place to determine which items will be added to a sprint.…

Hi @Amira Badran, while I have never been a fan of creating issues in the middle of a board / workflow, I can understand that this may be a user friendly way for people to add work items to a board. I have seen this functionality before and did learn back then that there were a lot of requirements related to the way the…

Hi @Viola Panzeri, no - but now we're getting somewhere: as you can see in your last screenshot, epics are still not returned by the filter behind your board: If you replace the board filter with one that does indeed include the epics, you should be fine.

For how to questions or help with functional challenges, you are very much in the right place. But to report bugs or feature requests, you can reach support via https://support.atlassian.com/contact/#/

Well, there is a new feature (rolled out or being rolled out) that allows child issues to be created from hierarchy issues above epics. I am not an Atlassian, so not involved in development, but it is possible that behaviour has changed as a result of such changes. And so indeed, that is not on your end, but the reason why…

Hi @Alex Harrison, Quite likely there is a required field that you cannot enter directly from the list here that is blocking the creation of a new story. What error/warning message does Jira display when you select the (!) on the right hand side of your screenshot there? I would expect the reason why it doesn't work will…

Hi @mohan.reddy, You should be able to use the approval completed trigger in automation to act as the thing that fires your automation rule. Once it's triggered, you should be able to do anything automation lets you, like add a comment, edit a field, send an email, transition the issue, ... Hope this helps! 

Hi @Sukanya KM and welcome to the Community! You can hide the summary from your form by checking the box Use preset value and hide from portal. You may fill out the request name already as the default value. Then, using an automation rule, you can update the summary after issues get created to add the reporter's name to…

Hi @Viola Panzeri, A couple of things to check: I see you marked epic as an issue type in the issue navigator view. In your screenshot, I don't see any epics reflected (it's possible that they are in the list, but not on the screenshot - I know. But still: make absolutely sure that they ARE being returned by the filter.…

FYI: see the settings of the progress field. Progress based on resolution only and weight determined by Story Points:

Hi @Aiman Syed, You would need to set progress calculation based on status / resolution for your scenario. As long as an issue is not completed, the number of story points delivered is actually still 0 (zero) - that is also how Jira deals with this. To roll up the progress of story points, you should configure the total…

Hi @Lana Kelly, no indeed it isn't 😅 - if you insist on using smart values instead of the approach I shared in the screenshot above, try: {{destinationIssue.issueType.name}} to refer to the issue type.

There is some back and forth on this thread about the enhanced backlog, so it is very well possible that some stuff has changed indeed. Maybe the quick filter workaround may be useful for your situation as well. 

I know quite a few ways to eliminate sub-tasks from a board, indeed. That's my point - I am trying to see if I can reproduce what you see in a test environment I have. It would be helpful if you could share exactly how it's been set up in your environment. I'm not questioning that nothing changed in your setup 😛 I noticed…

Hi @Viola Panzeri and welcome to the Community! Have a look at your board filter (in Configure Board > General). Most likely, your epics are not returned by the filter. In such a case, you won't see your epics in the backlog and won't be able to display them in the side panel. So, adjust your filter so Epics are returned…

I am seeing sub-tasks on my kanban backlog too; how did you technically implement this exactly: query states do not return Sub-Tasks

Hi @Lee Street, Can you share more details about your setup? What product do you use for this kanban board (Jira Software, Jira Service Management, Jira Work Management) and what type of project is this (company or team managed)? Ideally, can you share a screenshot of the behaviour you're seeing? 

Hi @Saili , No, not if you use a scheduled trigger with a JQL filter directly included in that trigger. This makes the following actions automatically apply to all issues returned by the filter.

Good follow-up, @Kim Killen. * Log work is the action you perform to fill out the time spent field. In Jira, this is part of the timetracking field when you want to add it to screens. * As I more or less mentioned in the previous question: log work is not a field. It is an action. Original estimate is the field you use to…

Hi @c.ermeier, Isn't it an option to just reduce the value of the parent field's story points field with the number of points on the issue you just moved into the Done column? Hope this helps! 

Hi @Kim Killen, Basically, the short answer is none. Burndown and velocity charts - which are available by default on a scrum board - look at the columns of the board and consider an issue as done when it reaches the rightmost column of the board. This results in the value the issue reports (in story points or issue count)…

Hi @Saili, If you create a rule with a scheduled trigger, you can add a JQL filter to the trigger. If you want to get a list of all epics in your project, that could be: Project = "Your Project" AND issuetype = Epic adjust the JQL so you get just the list of epics you want to add issues to. Then, if you add a create issue…

In the meantime - for a technical answer to your question, you can set up an automation that looks like this: I don't have the same issue types and link types you mentioned in your initial ask, but those are the only things you would need to adjust to your scenario. Hope this helps - but still very much interested in your…