Does anyone know of a good time tracking add-on for Bitbucket?
Something where I can put time manually and associated cost per hour, which would then give me the total?
You can use TMetric time tracker addon for Chrome to use it in Bitbucket.
There is a small tutorial of how to start to use it https://tmetric.com/integrations/asana-time-tracking/
There is no page dedicated to Bitbucket time tracking but it is pretty the same like with Asana.
Related
I have problem with Jira Cloud and Bitbacket. When I make smart commit - Jira only synchronize data commits with 60 min interval. Can I change this setting in Jira Cloud?
May be anybody had such problem? Thank You!
Seems that in cloud instances web hook from Bitbucket is responsible to trigger sync. I believe Benjamin Morgan replied to similar questions in Atlassian issue tracking. I would recommend you to take a look at it (here).
However, since Atlassian Cloud instances change regularly it's difficult to verify if it's still a valid configuration or not.
I have never written a windows service or any scheduler before so I couldn't figure out what to do.
I need to write a windows service. There is a Report table in my DB, and I need to check it every day to see if there are new reports added. Reports have receivers and the time settings, such as 15th of every month at 14:00, or daily at 12:35 or weekly on Wednesdays at 13:00. And I need to send emails with some reports at these times.
As I have decided, I will use Quartz.NET. But there are a couple of things I don't understand. So I will have 2 Jobs I think. One for checking the DB every day, to see if there are new reports that users want. And when I receive them, I'll create new different amount of Jobs with new triggers based on the times in the DB? Do I create new triggers in the job of the first daily check? I didn't understand it.
And when for example a time of one report is updated, or deleted, Do I need to delete the Job and the trigger from the scheduler? I'd appreciate the help. I am using VS 2015 with C#.
And when I do the windows service, I'll just initiate this Quartz thing that I have written? Sorry I couldn't understand what I have read so far.
I would recommend Hangfire IO over Quartz.net
http://hangfire.io/
Its a more modern approach to scheduled jobs. In the past I've used Quartz.net as well. First of all, using hangfire requires no service. The jobs are persistent, and retries are built in. The syntax is also easier.
I've used hangfire and its wonderful and simple.
however, Hangfire does not support Oracle db so far. Also Quartz provide more flexibility in terms of scheduling (calendars, end dates etc).
Hello i would like to know if its possible to have watches to monitor which task programmer is working on.. like some time tracker like https://play.google.com/store/apps/details?id=com.rauscha.apps.timesheet but integrated with TFS web service and for desktop.. im just trying to use TFS only for project scrum support but i need to know how many hours programmers spended on which task.. i guess in reality PM dont fill it manually so how it works in real projects ? Thank you
Actually in real projects developers are required to track their own time. In an ideal situation the elapsed time would be the completed time - the assign time. This doesn't work generally as developers generally work on more than one task at a time.
After finishing some task, how is it possible in jira log this current(finish) time?
So I don't want calculate time spending on task as start time of task + time spended on task, I want only enter finish time and time spent will be calculated(in jira) as finish time-start time.
JIRA doesn't currently offer real-time time tracking.
However your IDE should have some means of logging you time - for example Eclipse has this built in in the tasks plugin and it could also be connected to JIRa so that you could see your tasks in the IDE and log your time in "real-time" right there.
I have found this to be rather inconvenient since if inactive inside the IDE for a certain period of time the tracking will stop - this is an option in the IDE though.
I personally use Toggl which is free for a "one-man show" team. Also their pricing for teams is very nice. There are other services like Toggl and they are not all web-based. For example Project Hamster if you're on Linux. Just google time tracking. ;) Otherwise as I said the only way is to connect your IDE to JIRA via some task module.
Like every commit has a reason and purpose, I think each deploy has a purpose and reason. Source code commits have a comment. But deploying doesn't have any.
How do I record a reason and purpose for each deploy automatically?
I need to keep a record of:
Who deployed to where and what time.
Why deployed? Bug fixes? Feature update? Emergency fix not on iteration plan?
Which git or svn ref was used?
Have anybody felt the need for this kind of system? How do you feel about my approach?
How can I achieve my goal? I'm currently using Capistrano for deployment.
A bounty added. I'd like to hear more stories from different developers who are doing "continuous deployment".
I found two services that do deploy tracking:
Codebase
Hoptoad
Webistrano - https://github.com/peritor/webistrano/wiki - is a web interface to capistrano, that also tracks who's deployed what and when, so that could be worth investigating.
My current project uses a modified version of the apinsein's git-deployment recipe, which (when you tell cap to do a deploy) will tag current HEAD with a Git tag (which gives you all the benefits of normal Git commits).
I've built a web service for this exact problem, http://deploytracking.com, it hooks into capistrano and records the time, user, branch, ref, environment and repo that was involved in the deployment.
Strano - The Github backed Capistrano deployment management UI.
Regarding continuous deployment, I also submitted pull request there, which Introduce automatic deployments for GitHub projects, for now it simply triggers deploy task when somebody push to the master branch.
I don't know if it is still relevant but I would like to come up with a different solution. I am building a new deployment tool that does just what you are looking for.
I do not intend to spam my stuff here but since I am building something that could help you...
Anyway, have a look here https://alessiosantocs.github.io/Captain. I'm gathering feedback so if you have any please let me know.
Update
As suggested, I'm giving an explanation :)
I have also felt this need. I work in a digital startup and we're constantly deploying stuff 5 days a week on different Ruby on Rails application with Capistrano.
What we noticed was that for every single deployment, we should have done several things:
Keep track of which pull requests and commits went online that exact moment
Give some sort of a name to the deploy so we could recognize it
Alert our team members so that everyone could have been on the same page (without asking us of deployment's news)
Keep track of every deployments for future bugs and errors we might find at some point in time (which happened often)
So for this reason we started developing this custom solution that would integrate with Capistrano and our SCM (bitbucket) and keep track of every change we made to our master branch. This is what it does right now.
We are currently tracking deployment environment, repo source, deployment branch and revision. Mainly we manage pull requests, because we found that pull requests, better than commits, did solve an organizational issue in our team (it was difficult to approve other team member's code without a rigid system like PRs)
I would like to explain more about Captain and about our personal dev management strategy with you guys if you want.
Thanks #thirumalaimurugan for asking for clarification!
Update 2
We tried git tagging too. It was good and fun at the beginning but we couldn't manage them very well.
A tag is basically a bookmark to a specific revision. So we're talking about commits. A tag keeps no track of pull requests. It was quite a mess for us.
I don't think they're bad at what you're trying to achieve, but I think there must be some other solutions that could fit exactly your (and our too) problem.