Default values of component should be translatable

First of all, I'm not sure why you put this in the Project queue--it belongs in the Project issue tracking queue. This also isn't really a task; I'd typically call it a support request, but since you're right about the component parameters not being translatable, I'll call it a bug report instead.

I feel like this might be a duplicate, since I know that Hass has reported a lot of issues about strings not being translatable, but I can't find another issue about this.

So, I'm not sure what you're actually asking in your question. If your complaint was that the default values of the Component field are not translatable, the attached patch should fix that.

If your question was about how to add additional components or change the default components (but not by translating them), then that's easy. Components can be changed per project. So, after creating a project, click the edit link to edit the project, then select the Issues link/tab, and then add/change the items in the components text area.

As for priority parameters, I believe that those are translatable already. However, it's not possible to add/remove/change those (other than by using Drupal's localization features) without directly hacking the code in project_issue.module.

Hm...i'm not sure. I didn't actually test using the locale module to see if the strings would show up there, but I'm not sure why they wouldn't. I'll have to check this out on my development machine later today or tomorrow and see if the string show up.

Ok, I tested this patch on an otherwise clean installation and it does work. However, there are a few caveats you might not have realized:

1. t('Documentation'), etc. is only called when a project node is created. So if you haven't created a new project node since you applied the patch, then the strings would never have been passed through t() and thus you won't see the strings to be able to translate them.

2. Any translations you make to these 4 default component strings will only take effect for *new* projects created after you translate the strings. Once the project node is created, the possible values for the component field for that project are stored in the database, and are therefore not passed through t() again at any point.

So basically this patch will only let you translate the default values of the component field, and only for project created after you translate the strings.

looks good. committed to 5.x-1.x, 5.x-2.x, HEAD.