Groups keyboard shortcuts have been updated
Dismiss
See shortcuts
Advantages of Jobsworth over Redmine
51 views
Skip to first unread message
Slind
Oct 17, 2015, 3:56:33 AM10/17/15
to jobsworth
Moin everyone,
I had been using clockingIT in the past since then a lot of time has passed and development concluded. As it is difficult to judge (for me) if using jobsworth or redmine is the proper platform for further management I would like to get your opinion. I find it rather impossible to get a real feeling for an app without using it in production so I hope that some of you might have used both and can give some personal insight.
Where do you see the advantages of jobsworth over redmine and for which use-case would prefer it?
Thanks in advance
Slind
Vikrant Chaudhary
Oct 19, 2015, 1:02:15 PM10/19/15
to jobs...@googlegroups.com
I haven't used Redmine recently, so probably the best to way to find out what suits your needs is to try out both of them. (Jobsworth has support for time tracking, but seems like Redmine does too - https://www.redmine.org/projects/redmine/wiki/RedmineTimeTracking)
--
---
You received this message because you are subscribed to the Google Groups "jobsworth" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jobsworth+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Aristedes Maniatis
Oct 19, 2015, 8:22:36 PM10/19/15
to jobs...@googlegroups.com
On 20/10/2015 4:01am, Vikrant Chaudhary wrote:
> I haven't used Redmine recently, so probably the best to way to find out what suits your needs is to try out both of them. (Jobsworth has support for time tracking, but seems like Redmine does too - https://www.redmine.org/projects/redmine/wiki/RedmineTimeTracking)
>
> Though, one major difference that I'd like to point out is that Jobsworth's primary platform is now JRuby (which requires a JVM).
Actually Redmine also supports jrurby: http://www.redmine.org/projects/redmine/wiki/HowTo_install_Redmine_in_Apache_Tomcat
> I haven't used Redmine recently, so probably the best to way to find out what suits your needs is to try out both of them. (Jobsworth has support for time tracking, but seems like Redmine does too - https://www.redmine.org/projects/redmine/wiki/RedmineTimeTracking)
>
> Though, one major difference that I'd like to point out is that Jobsworth's primary platform is now JRuby (which requires a JVM).
One difference I know about is that jobsworth has no anonymous access. But I also think we have a lot more functionality in resource management, contact management, etc
Ari
--
-------------------------->
Aristedes Maniatis
ish
http://www.ish.com.au
Level 1, 30 Wilson Street Newtown 2042 Australia
phone +61 2 9550 5001 fax +61 2 9550 4001
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
Slind
Oct 20, 2015, 10:08:15 AM10/20/15
to jobsworth
Not having used jobswroth but clockingIT this is about what I remember to be the major difference. Time tracking is not as advanced as in jobsworth (well maybe it is by now with 3.x). There is no CRM without addons. The resource management is there but not in the way clocking it had it with working hours (as far as I remember)..
The advantages of redmine (assumed), complex issue/task filtering. Sprints/Versions. Issue/Task relations (follows 499 with 5 days distance..), SubProjects (you organize customers by projects and use sub projects for their projects), auto assignment, a full REST API for everything.
The complex filtering being the biggest one, which I don't necessarily need, hence my thought about getting back to jobsworth.
Aristedes Maniatis
Oct 21, 2015, 6:44:29 PM10/21/15
to jobs...@googlegroups.com
On 21/10/2015 1:08am, Slind wrote:
> The advantages of redmine (assumed), complex issue/task filtering. Sprints/Versions. Issue/Task relations (follows 499 with 5 days distance..), SubProjects (you organize customers by projects and use sub projects for their projects), auto assignment, a full REST API for everything.
I'm interested in these things. Can you tell us more about the filtering options in Redmine and what you think might be useful. We have a very powerful search, but it isn't as intuitive as I'd like.
> The advantages of redmine (assumed), complex issue/task filtering. Sprints/Versions. Issue/Task relations (follows 499 with 5 days distance..), SubProjects (you organize customers by projects and use sub projects for their projects), auto assignment, a full REST API for everything.
We also do have a REST api (by default every Rails app does), but it isn't documented that would let people write (say) a mobile app to talk to it.
Subprojects and milestones are certainly something that would be interesting to add, but a lot of work. I wonder if that's the best approach, or rather we should enhance our 'tag' concept to provide something similar.
N Lind
Oct 21, 2015, 9:49:04 PM10/21/15
to jobs...@googlegroups.com
About the sorting, take a look at the official redmine issue tracker,
with the Filters directly below the navigation:
http://www.redmine.org/projects/redmine/issues
You can kinda what you could do with basic sql, what to show, what not
and how to group. You can also save those queries in different ways:
public for everyone, just for me.. (see the Custom queries in the right
sidebar)
It also allows further customization in terms of what the table should
show. Would you like to see the assignee, the project or is there a
custom field you would like to get a hold in directly (like the
resolution in this case).
You can also select multiple issues from the list and with a right click
quickly assign those or use any of the other many features
https://i.imgur.com/Z3VgEtq.png
So if you have tons of issue with man laying around for months/years, I
bet redmine comes in handy with keeping the amount of issues clear.
I for one find it rather difficult to work with tags once you exceed the
30th open ticket/issue.
Regarding App, well there are a few for redmine but non of them work
perfect, especially not with many custom fields and custom requirements.
E.g. I have a field that only shows up and is only a requirement once
the status of the ticket is set to closed, the apps can't deal with that
although it is a basic redmine feature.
Which brings us to another nice feature. Redmine allows you to define
workflows. So you can define what a group can do. E.g. the reporter can
only set the status to new, can only use tracker x and can only use the
priority "undefined". Then you have a project manager that is able to
sort the issue in if all required information is included, give it a
proper priority, adjust the tracker, set the expected time requirement,
assign the responsible department/group/person, include more
information, rewrite the description to be more clear and short and set
the status to filed.. I hope that gives you an idea of the main/most
powerful features.
Overall we can say that those are mainly useful if you have a high
amount of issues/tickets, if you have a lot of co-workers, if you have a
strict hierarchy or want it to be super tidy. I would also prefer it
above clockingIT with public issue reports, because I can keep them out
of the filters until they are useful and clear.
The reasons I'm thinking about using jobsworth for a new project is that
I don't have a big need for most of those highly powerful tools redmine
offers.
with the Filters directly below the navigation:
http://www.redmine.org/projects/redmine/issues
You can kinda what you could do with basic sql, what to show, what not
and how to group. You can also save those queries in different ways:
public for everyone, just for me.. (see the Custom queries in the right
sidebar)
It also allows further customization in terms of what the table should
show. Would you like to see the assignee, the project or is there a
custom field you would like to get a hold in directly (like the
resolution in this case).
You can also select multiple issues from the list and with a right click
quickly assign those or use any of the other many features
https://i.imgur.com/Z3VgEtq.png
So if you have tons of issue with man laying around for months/years, I
bet redmine comes in handy with keeping the amount of issues clear.
I for one find it rather difficult to work with tags once you exceed the
30th open ticket/issue.
Regarding App, well there are a few for redmine but non of them work
perfect, especially not with many custom fields and custom requirements.
E.g. I have a field that only shows up and is only a requirement once
the status of the ticket is set to closed, the apps can't deal with that
although it is a basic redmine feature.
Which brings us to another nice feature. Redmine allows you to define
workflows. So you can define what a group can do. E.g. the reporter can
only set the status to new, can only use tracker x and can only use the
priority "undefined". Then you have a project manager that is able to
sort the issue in if all required information is included, give it a
proper priority, adjust the tracker, set the expected time requirement,
assign the responsible department/group/person, include more
information, rewrite the description to be more clear and short and set
the status to filed.. I hope that gives you an idea of the main/most
powerful features.
Overall we can say that those are mainly useful if you have a high
amount of issues/tickets, if you have a lot of co-workers, if you have a
strict hierarchy or want it to be super tidy. I would also prefer it
above clockingIT with public issue reports, because I can keep them out
of the filters until they are useful and clear.
The reasons I'm thinking about using jobsworth for a new project is that
I don't have a big need for most of those highly powerful tools redmine
offers.
Aristedes Maniatis
Nov 22, 2015, 10:09:45 PM11/22/15
to jobs...@googlegroups.com
I just realised that I never replied to this... sorry about that.
On 22/10/2015 12:48pm, 'N Lind' via jobsworth wrote:
> About the sorting, take a look at the official redmine issue tracker, with the Filters directly below the navigation:
> http://www.redmine.org/projects/redmine/issues
>
> You can kinda what you could do with basic sql, what to show, what not and how to group. You can also save those queries in different ways: public for everyone, just for me.. (see the Custom queries in the right sidebar)
> It also allows further customization in terms of what the table should show. Would you like to see the assignee, the project or is there a custom field you would like to get a hold in directly (like the resolution in this case).
We have pretty much the same level of filtering and changing columns. Just ours is a bit more hidden... perhaps we need better ways to expose the power we have.
> You can also select multiple issues from the list and with a right click quickly assign those or use any of the other many features https://i.imgur.com/Z3VgEtq.png
A bulk editing feature is certainly something we could do with.
> So if you have tons of issue with man laying around for months/years, I bet redmine comes in handy with keeping the amount of issues clear.
> I for one find it rather difficult to work with tags once you exceed the 30th open ticket/issue.
>
> Regarding App, well there are a few for redmine but non of them work perfect, especially not with many custom fields and custom requirements. E.g. I have a field that only shows up and is only a requirement once the status of the ticket is set to closed, the apps can't deal with that although it is a basic redmine feature.
>
> Which brings us to another nice feature. Redmine allows you to define workflows. So you can define what a group can do. E.g. the reporter can only set the status to new, can only use tracker x and can only use the priority "undefined". Then you have a project manager that is able to sort the issue in if all required information is included, give it a proper priority, adjust the tracker, set the expected time requirement, assign the responsible department/group/person, include more information, rewrite the description to be more clear and short and set the status to filed.. I hope that gives you an idea of the main/most powerful features.
Although we already have many of those permission options, what we could do with is proper workflows as they are implemented in Jira. That is, have a button which is bound to a state transition and bundles up an entire workflow process. For example, an "implemented" button for a developer could assign the task to QA, email the right person, put a note in the history, etc.
That only touches on the power of Jira in this regard, but it is very powerful and we could learn a lot from it.
Cheers
Ari
> Overall we can say that those are mainly useful if you have a high amount of issues/tickets, if you have a lot of co-workers, if you have a strict hierarchy or want it to be super tidy. I would also prefer it above clockingIT with public issue reports, because I can keep them out of the filters until they are useful and clear.
>
> The reasons I'm thinking about using jobsworth for a new project is that I don't have a big need for most of those highly powerful tools redmine offers.
>
> On 22.10.2015 00:44, Aristedes Maniatis wrote:
>> On 21/10/2015 1:08am, Slind wrote:
>>> The advantages of redmine (assumed), complex issue/task filtering. Sprints/Versions. Issue/Task relations (follows 499 with 5 days distance..), SubProjects (you organize customers by projects and use sub projects for their projects), auto assignment, a full REST API for everything.
>> I'm interested in these things. Can you tell us more about the filtering options in Redmine and what you think might be useful. We have a very powerful search, but it isn't as intuitive as I'd like.
>>
>> We also do have a REST api (by default every Rails app does), but it isn't documented that would let people write (say) a mobile app to talk to it.
>>
>> Subprojects and milestones are certainly something that would be interesting to add, but a lot of work. I wonder if that's the best approach, or rather we should enhance our 'tag' concept to provide something similar.
>>
>>
>> Ari
>>
>>
>
On 22/10/2015 12:48pm, 'N Lind' via jobsworth wrote:
> About the sorting, take a look at the official redmine issue tracker, with the Filters directly below the navigation:
> http://www.redmine.org/projects/redmine/issues
>
> You can kinda what you could do with basic sql, what to show, what not and how to group. You can also save those queries in different ways: public for everyone, just for me.. (see the Custom queries in the right sidebar)
> It also allows further customization in terms of what the table should show. Would you like to see the assignee, the project or is there a custom field you would like to get a hold in directly (like the resolution in this case).
> You can also select multiple issues from the list and with a right click quickly assign those or use any of the other many features https://i.imgur.com/Z3VgEtq.png
> So if you have tons of issue with man laying around for months/years, I bet redmine comes in handy with keeping the amount of issues clear.
> I for one find it rather difficult to work with tags once you exceed the 30th open ticket/issue.
>
> Regarding App, well there are a few for redmine but non of them work perfect, especially not with many custom fields and custom requirements. E.g. I have a field that only shows up and is only a requirement once the status of the ticket is set to closed, the apps can't deal with that although it is a basic redmine feature.
>
> Which brings us to another nice feature. Redmine allows you to define workflows. So you can define what a group can do. E.g. the reporter can only set the status to new, can only use tracker x and can only use the priority "undefined". Then you have a project manager that is able to sort the issue in if all required information is included, give it a proper priority, adjust the tracker, set the expected time requirement, assign the responsible department/group/person, include more information, rewrite the description to be more clear and short and set the status to filed.. I hope that gives you an idea of the main/most powerful features.
That only touches on the power of Jira in this regard, but it is very powerful and we could learn a lot from it.
Cheers
Ari
> Overall we can say that those are mainly useful if you have a high amount of issues/tickets, if you have a lot of co-workers, if you have a strict hierarchy or want it to be super tidy. I would also prefer it above clockingIT with public issue reports, because I can keep them out of the filters until they are useful and clear.
>
> The reasons I'm thinking about using jobsworth for a new project is that I don't have a big need for most of those highly powerful tools redmine offers.
>
> On 22.10.2015 00:44, Aristedes Maniatis wrote:
>> On 21/10/2015 1:08am, Slind wrote:
>>> The advantages of redmine (assumed), complex issue/task filtering. Sprints/Versions. Issue/Task relations (follows 499 with 5 days distance..), SubProjects (you organize customers by projects and use sub projects for their projects), auto assignment, a full REST API for everything.
>> I'm interested in these things. Can you tell us more about the filtering options in Redmine and what you think might be useful. We have a very powerful search, but it isn't as intuitive as I'd like.
>>
>> We also do have a REST api (by default every Rails app does), but it isn't documented that would let people write (say) a mobile app to talk to it.
>>
>> Subprojects and milestones are certainly something that would be interesting to add, but a lot of work. I wonder if that's the best approach, or rather we should enhance our 'tag' concept to provide something similar.
>>
>>
>> Ari
>>
>>
>
Slind noone
Nov 22, 2015, 10:39:46 PM11/22/15
to jobs...@googlegroups.com
Yeah redmine can do that too with those work flows.
Reply all
Reply to author
Forward
0 new messages