วีดีโอ

Thanks for your comment Sudhanshu. Yes moving tickets between can also be automated based on customised rules. For example: Let’s say we need to automatically move a ticket to “Ready for QA” column once the PR is approved, we can write an automated rule to make this happen. Hope this help!

Hello, thank you for your questions. When you select “link” and “Sprint values”, those details are also maintained in the new issue which is created because of cloning. And both the cloned issue and the issue being cloned are linked. In case you want to edit that you can later edit from the issue screen. Hope this helps!

Hello, thank you for your question. % is the distribution of work with respect to assignee. It is the amount of work assigned to a person against the total work in the filter created. For example, if there are 5 tickets in the filter created and total of original estimate is coming up to 100hrs, 2 tickets are assigned to you and sum total of those two tickets are18 hours, then % against your name would be 18%.

Hello, thanks for you reply. We understand that different teams use different versions of Jira. The steps mentioned in the video are common for all the versions. Could you please elaborate on your observations and share as to what difference you see?

Happy to help!

Thanks for reaching out. If you do not see “workflows” in your project settings, that means you do not have access to it. Please reach out to your JIRA admin for permissions or ask them to make the changes you are looking for.

Thank you so much for your kind words! We are glad you found the video helpful. If you have any more questions, feel free to ask. Happy learning! 😊

Hi, Thanks for reaching out. The workload pie chart shows the effort members have logged on their piece of work. In the scenario you mentioned, you will have to create tasks/sub tasks under the story and assign it to respective members where they can fill their effort individually. Yes, this will show the total time spent on the ticket be it a spillover or not. It’s just that you will have to create multiple tickets and assign it appropriately. Hope this helped!

Hi, Yes, the task can be in test as it is getting tested in dev environment. In case you want to add another status in your workflow to differentiate, you can add a different status. (Ex: To Do > In Dev > Test in Dev > Test in QA > done) Hope this helped!

@@BenzneConsulting thank you so much

Hi MB Kaushik, thanks for your comment. You are not doing anything wrong. Please note that this is the default behaviour of Jira. When a ticket is moved from one project to another, the ticket is prefixed with the Key of the 2nd project where it is moved. Jira does it automatically. Hope this helped.

Hello, Thanks for your comments. Yes your understanding is correct here. This workload pie chart pulls the latest assignee and time spent by him/her. If you are looking at time spent by both of them, you might have to capture in two different tickets. Hope this helped.

Hello Allia, Thanks for writing to us. The steps involved in migrating are very similar to the ones mentioned in the video. However, mentioning it in the comments for your reference. Go to the list of the tickets/incidents in your old service management project ( in issue navigator) > select all the tickets you want to move> in the moving wizard, select the new project > click on proceed > acknowledge. Please let us know if this works or you need more information.

Thanks for the request. We will very soon release a video on Jira help desk & service management. Appreciate your patience!

Hi, We already have a video on the same topic. Please refer to it. Pasting the link below 👇 th-cam.com/video/wrqc8nZ1v9U/w-d-xo.htmlsi=zvW4_CCNjdjV3gyO

Glad you think so!

Hi Sanket, The best solution to avoid any confusion, we recommend is to create a custom field called “Team” which can have all your team names as options Ex: If you have 3 teams working on the same project, then create a custom drop-down field called “Team” with “Team 1”, “Team 2”, and “Team 3”. Once you are done with this then your filter can look something like, Project = <your project> & team <select the team> (Project = Amazon & team = Avengers) in this case, any ticket which has team name as “avengers” will come into the board created for them. Hope this helped

Yes, definitely.

Glad to know & happy to help!

1. You should have “Create Shared Objects / Share Dashboards and Filters” permission enabled for you in order to create a board. Or you must have “Project Administration” access. 2. You can ask your site admin / Jira admin to give you access. Or if you are the site admin, you will have to update it by going to System > Global Permission > Scroll down the page > Select “Share dashboards and filters > Select your group

Step 1: Filter out all the tickets you want to move ( Asignee=Unassigned) Step 2: Follow the steps mentioned in video for “Bulk Operation”

You are welcome!

Glad to know, Thank You!

Glad it was helpful.

Greetings Launa, as mentioned in the video, you can either use team-specific labels or components to filter the work items into respective boards. Another option is to filter work items based on workflows. The simplest of all options is to create a custom field and filter based on the field. Eg: Create a custom field called “Scrum Team=Avengers, Xmen” Filter for the board will be Project=(your project) AND Scrum Team=(Avengers/Xmen)”

Thank You!

Glad it was helpful!

Glad you think so!

Thanks, we understand your point. Our recommendation is not one size - fit all solution and is based on our experience across numerous projects. However, there are bound to be projects where this may not apply.

Thank You.

Thank You, Ravinder. Indeed we are.

Glad you like it.

No, with the guest board, you will not be able to edit the section name, once the board is created