Jack Hunter _HeroCoders_ Atlassian Partner

There is also available free version of the Issue Checklist app: https://marketplace.atlassian.com/apps/1220209/issue-checklist-free?hosting=cloud&tab=overview

It does copy/apply the default checklist to newly created issues only. Changing or defining a default checklist does not affect existing issues. If you want to add the checklist to existing issues, then, please follow the below…

@Margarita Artemyan, please try to create the template first, according to this documentation: https://gebsun-support.atlassian.net/wiki/spaces/IC/pages/768049153/Creating+a+template When the template is there, then please follow the instruction from the video I shared in my previous comment. Let me know if that helps.…

Hi @Margarita Artemyan I have recorded a short video presenting how to create a default checklist: https://www.dropbox.com/s/9tsy5gq9sc58lo7/ScreenFlow-small-lowquality.mp4?dl=0 It is 7.3MB large. Let me know if that helps. Cheers, Jack

So, it sounds like you need exactly the two features that I described and pictured in the previous comment: * default template/checklist per issue type (select Story in the configuration dialog) * block issue transition/resolving if the checklist is not completed Let us know in case of any questions or requirements. We are…

Hi, When comes to the definition of done presented in form of the checklist then all mentioned apps can do it. However, if you want to apply checklist/template only to Stories (but not Bugs for example) or have Tasks and Stories received a checklist different from each other then only Issue Checklist can do it. And it does…

Hello @Margarita Artemyan, I can also propose Issue Checklist, developed by my team, that comes with unique features not available in other apps, e.g. default checklist defined per issue type (so Bugs and Stories can get different checklist automatically upon creation). It also comes with a real user mention (through the…

Hello @Avinash Perera, Here is a link to docs: https://herocoders.atlassian.net/wiki/spaces/CLK/pages/44761089/When+do+automatic+timers+start+stop Clockwork is a young tool and its documentation is not complete. If you have any question that is not covered by documentation then feel free to ask here or contact support team…

@Rafael Campos All users with the proper permissions can log time directly in Jira. You don't need plugins for that. The plugins, on the other hand, can improve time logging and reporting process. Clockwork Automated Timesheets, for example, allows tracking time automatically when the issue is transitioned through the…

OK, so we have one possible way of implementing your requirement, i.e. "blocking log works shorter than 30m". I wonder if another solution could work too. You mentioned that the problem is mostly with people spending time on logging the work. What if the time was logged automatically? We have an app Clockwork Automated…

@jesusem thank you for an explanation. Just to have a final clarification: you would like to skip/block the work logs shorter than 30 minutes, right? 

Hello @jesusem , Could you explain why you need this functionality? I wonder what is the rationale behind such a requirement. We might consider building a plugin that solves that problem if it is justified. Thanks, Jack

Hello @Tim Kersten As Alexey mentioned, time tracking is not available in Next-Gen projects. More, it is not on a roadmap so we don't know if and when Atlassian is planning to make it available. However, there is an issue to track and vote: https://jira.atlassian.com/browse/JSWCLOUD-17447 In the meantime, until the feature…

Hello @Avinash Perera I can also propose Clockwork Automated Timesheets. It is a free tool that allows tracking time precisely in an automated way, integrated with Jira workflow (time starts and stops when an issue is moved between statuses). Users can also use the Start/Stop timer button if they prefer too. Tracked time…

Thank @Craig Patchett. I have updated the answer to reflect that. 

Hello @Lee Correll As Claudiu from Atlassian team explained, it is not possible to move the field to the left side in New Issue view. So you need to live with the problem, unfortunately, or put the content to the field to the Description (again as Claudiu suggested) or try to use some other solution for acceptance…

Issue Checklist for Jira Cloud gives that possibility. It allows to: * Create a default checklist for selected issue types in a given project (so checklist is applied automatically when the issue is created). * Block resolving an issue if not all checklist items are completed It also comes with a free version Issue…

The first thing that comes to my mind is timezone.

Perfect. Give it a try then and share your requirements and comments. Clockwork is under active development and every new idea can get in making it even better. Cheers, Jack

Hello @Sergey Sheypak, Clockwork is a free app at the moment so you won't be charged for using it. If it is installed successfully, you can visit any Jira issue and see the Clockwork panel that helps to track time and watch the progress. You can also visit the Clockwork project page that shows the summary in the form of…

What kind of report do you need exactly? It might be available in Clockwork Automated Timesheets already or we might want to add it. Thanks, Jack

Hello @Lawrence Horwitz, Clockwork allows entering time manually now in both Next-Gen and Classic projects. Cheers, Jack

Well, "comparing primary estimation with the actual work time" When it comes to the estimation, I would suggest story points and velocity. More can be found in a post shared by Earl in his answer: https://www.atlassian.com/agile/project-management/estimation Long term, the velocity allows planning the project in a…

It might be a HubStaff problem. As Jack explained in his answer, the default Jira behavior is to reduce Remaining Estimate by the Time Logged. It assumes that the initial Remaining Estimate was set correctly. If you are on Cloud and not tied to Hubstaff too much, then you can try Clockwork Automated Timesheets. This is a…

Hello Sorcha, So: * You cannot use estimates reliably because you don't know exactly how much time you will spend on the issue. That's OK. With this approach, it would be harder to predict the project timeline but you are the only one working this way so is acceptable I think. * You use different workflow than the rest of…

When comes to time tracking, Clockwork records time in Jira worklog so it is available to both Jira and third-party add-ons. It works in the same way as standard Jira "Log Work" functionality, just in an automated and easier way. It also makes the time records more precise by removing the "I forgot to log work" or "I…

It seems like the Jira time tracking (original estimate, remaining estimate, log work) should work for you. Here is how to: * enable Jira time tracking * use Jira time tracking Clockwork can ease the pain when comes to logging work (registering time worked). It starts the timer when an issue is moved to In Progress, and…

Hello @Manu G, If by any chance you are referring not to SLA but "remaining estimate" concept then it is available in Jira: https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html It basically requires you to set the "original estimate" for an issue (in…

Clockwork should support standard Log Work dialog soon I think.

Hello @Lawrence Horwitz, As Alexey mentioned this functionality is not on a roadmap but there is an issue to track and vote: https://jira.atlassian.com/browse/JSWCLOUD-17447 In the meantime, until the feature is added by Atlassian, you might want to use a third-party app that helps with time tracking in both Classic and…