I am trying to use Open Atrium for development project issue tracking. I am seriously struggling with some functionality. E.g. I am trying to find how to enable auto-numbering for tasks (which I use as tickets). Is there a way to do so? Also, I would really love to add additional fields to Work Tracker tasks - I need version and milestone fields. Is there a way to add those without programming? Would really appreciate your input!
I found an article here: https://groups.drupal.org/node/7850, but it seems that everything applies to the version OA 1.0 and doesn't apply anymore to the new OA.
Best regards
A side qeustion: I've decided to choose Open Atrium for development project tracking (vs. using Trac). Now it seems I start to regret the decision a little bit. OA seems much more visually attractive, but I really find the learning curve very steep... Maybe it just became to generic (company intranet) than it was when it was in the version 1.0... Is there some begginers guide (NOT Drupal generic please) which would explain things at the USER level? I am not a developer and want to customize things via GUI.
Comments
You can add new fields to Tasks! But...
You can add new fields to Tasks! This is done in the normal Drupal way via the UI, with a couple of minor considerations for use in Open Atrium 2, which I explained on a previous discussion post:
https://groups.drupal.org/node/422563#comment-1034788
This will definitely allow you to add your "Version" and "Milestone" fields.
However, at the moment, Open Atrium's Work Tracker isn't really a full solution for doing software development issue tracking. I think someone could create an add-on module to make it into one (and I'd happily consider merging it upstream, if the community did it!), but at this point it's really just geared to generic collaboration.
So, if you're looking for something like Trac, you're not going to get it in Open Atrium without quite a bit of site building. :-/
I hate recommending people away from my own software projects, but if you don't have the time or Drupal knowledge to do it, switching to Trac or JIRA or RedMine or something is probably the better option.
I hope that helps!
Cannot post
Cannot post a response due to it being recognized as spam :|
Maybe it will be successful now
(Wasn't able to post this due to it being recognized as spam)
Thank you very much for your quick response! Actually, if I manage to do some minor stuff (like add Version, Milestone fields and expose unique ID (autonumber) for task items), I will keep Open Atrium for development tracking as there's little other functionality I would be missing, at least at the moment.
Thank you for the link, I forgot that I have actually stumbled on it already and I have read you responses as well as Mike Potter's articles. The explanation was still overly complex as I am not familiar with Drupal at all. Is there some documentation with general basic guidance (with GUI explanations/how-tos relevant to the current OA version) on how to to use Features override to enable additional fields? What I've read so far is quite far from the approach "Open up configuration in the Admin section, pick the template you want to modify (tasks), choose Edit, choose to add fields, provide field type info, etc." - this approach would work in Trac. I understand, this kind of path wouldn't be sufficient in OA as some prerequisites have to be met beforehand?
The primary thing I am missing is - how do I start this modification process? There's a lot of "back-end" complex stuff explained, a lot of considerations for "what-if" cases, but I am missing simple info I could use to begin with all this - which Admin section should I go first :). I have tried looking into Home -> Administration -> Structure -> Features. Should I be using "Create feature" section somehow?
Thanks again!
You're going to have start digging into Drupal documentation
Hmm. So, unfortunately, I'm not aware of any Open Atrium documentation that shows you how to do Drupal things assuming you don't already know Drupal site building. :-/ You're going to have to start digging into Drupal documentation.
Drupal's core strength is data modeling, ie. creating Content Types and adding Fields to them. Here's some Drupal documentation about that:
https://www.drupal.org/documentation/modules/field-ui
https://www.drupal.org/node/774742
Those pages (and the pages linked from them) will hopefully help you get your new fields on to Tasks. Once you're in there, hopefully, the special considerations for OA from my previous comment will make sense!
With regard to Features and Features Override: this isn't something you do at beginning, but at the end AFTER you've made your modifications. And, actually, if you're only adding things and not changing existing things, you don't necessarily need to use Features Override.
The deal with that is this: Open Atrium's configuration is stored in Features. When you upgrade Open Atrium to a new version, generally, you revert all those Features which restores their configuration to default settings. So, if you changed any of it, then upgrading could remove your modifications.
But to answer your question:
Yes, you would use "Create feature" and then select all the things under "Features override" that you modified. You would download the resulting module, and then enable it on your site. This would preserve your modifications through an upgrade.
I hope that helps!
Regards,
David.
Late response
dsnopek, I had my reply ready the very same day you have posted. It appears "Thank you" in a subject will make spam filter believe it's spam :). Thanks again.