Define a default issue node type using D7 fields [#1320386]

Subtask of #963426: [meta] Port Project issue tracking to Drupal 7

We want to define a default node type for issues with a bunch of core (and some contrib) fields, instead of all the custom node type and field code we have now. I'm working on this at the D7 Project* sprint and wanted an issue for Git commits.

Mostly done in the 7.x-2.x branch of project_issue now.

TODO:
- need an OG audience to associate issues with a single parent project. this needs a magic widget so that if you change the value, the related fields are auto-updated appropriately (version, assigned, component)
- version string (need to debate if this should remain an entityreference to release nodes, or a string or what)
- assigned needs an allowed values callback so we can restrict the choices to the right subset of users
- component needs to harvest allowed values from the parent project node
- a sane way for drupalorg_project to alter the allowed values of status, to customize appropriately

Comments

Comment #1

dww

we/he/they

commented 25 October 2011 at 02:11

Status:

Active

» Needs work

Much of this is now done via:

http://drupal.org/commitlog/commit/1894/c14f551ce08e14beedb93d0f2c651c52...
http://drupal.org/commitlog/commit/1894/c5998df9af1d27881530fab6c42d3c9e...

The remaining tasks are now in the summary.

Comment #2

dww

we/he/they

commented 25 October 2011 at 22:42

Upon further consideration, discussion and investigation, requiring features and providing our own feature actually makes it harder for sites to manage their modifications to our default node type in code. If we just define the node type directly in hook_install() (like the standard profile does with article and page types) then it's easy for a site to 'hijack' that type, export it as a feature, and alter cleanly...

http://drupal.org/commitlog/commit/1894/4f53152cff433590a27fbc1f1b48176f...

Most of the TODO items in the summary are still valid.