Hi all, this is an odd question, but I am trying to move our organization over to JIRA.
My supervisors are really particular with the language that we use to describe Project Management and have asked if I could overwrite what JIRA calls "Projects" and instead call them "Programs" so that the language will be consistent with what is used internally.
Can I overwrite the verbiage native to JIRA, calling "Projects" something else? I know with other aspects I am able to create new titles (such as renaming issues, etc.) Thoughts?
Have you ever tried custom languages? The solution can be around this trick
- Custom language pack
- Using something like this
I think that the app "InProduct translation for Jira" is the best option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I'm reading this correctly, the Custom Language Pack seems to allow me to edit the descriptions of certain things, but not the actual title of those things. Maybe I'm missing something.
The second link that you provided for InProduct Translation for JIRA seems like a great fit. Is it an issue that it isn't formally supported?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If it isn't supported it can go away with any release. IMO, this is a COTS product and management should understand that and get over the nitpicking.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, it is COTS, but I think one of its major selling points is a high degree of customization. Language is really meaningful in terms of culture and adoption. Certainly not a need to have, but doesn't hurt to ask.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have to agree with Joe. There is no real value in doing this at all. If it were me (and I have done this several times), I would do a proper cost/benefit analysis.
Costs:
Benefits:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.