Details

    • Type: Sub-task Sub-task
    • Status: Open (View Workflow)
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Administration, Workflow
    • Labels:
      None

      Description

      I want to change the label of the summary field per screen.

        Issue Links

          Activity

          Hide
          Zhen Yueh, Lean [Atlassian] added a comment -

          Hi Kerstin,

          At the moment, you can do this by customizing the text in the language pack:

          Cheers,
          Zhen Yueh, Lean.

          Show
          Zhen Yueh, Lean [Atlassian] added a comment - Hi Kerstin, At the moment, you can do this by customizing the text in the language pack: http://confluence.atlassian.com/display/JIRA/Customizing+text Cheers, Zhen Yueh, Lean.
          Hide
          Kerstin Klein added a comment -

          Hi,

          Thanks for your immidiate response.

          Unfortunally, I only want to change the summary field label in two of five create issue screens. Imo the language pack manipulation allows only a global change, doesn't it?

          Regards,
          Kerstin

          Show
          Kerstin Klein added a comment - Hi, Thanks for your immidiate response. Unfortunally, I only want to change the summary field label in two of five create issue screens. Imo the language pack manipulation allows only a global change, doesn't it? Regards, Kerstin
          Hide
          Zhen Yueh, Lean [Atlassian] added a comment -

          Hi Kerstin,

          Yes, customizing the language pack will affect the whole JIRA (i.e, globally).

          Cheers,
          Zhen Yueh, Lean.

          Show
          Zhen Yueh, Lean [Atlassian] added a comment - Hi Kerstin, Yes, customizing the language pack will affect the whole JIRA (i.e, globally). Cheers, Zhen Yueh, Lean.
          Hide
          Glen Geisen added a comment -

          Zhen - does your last comment imply that only global changes are possible, and that one cannot change an individual label on only one screen?

          Show
          Glen Geisen added a comment - Zhen - does your last comment imply that only global changes are possible, and that one cannot change an individual label on only one screen?
          Hide
          Zhen Yueh, Lean [Atlassian] added a comment -

          Dear Glen,

          Yes.

          that one cannot change an individual label on only one screen?

          It can be done by customizing the JSP/VM files. Perhaps, you can try to raise this question at the jira-developer mailing list where the JIRA developers do take part in the customization discussion with other developers.

          Cheers,
          Zhen Yueh, Lean

          Show
          Zhen Yueh, Lean [Atlassian] added a comment - Dear Glen, Yes. that one cannot change an individual label on only one screen? It can be done by customizing the JSP/VM files. Perhaps, you can try to raise this question at the jira-developer mailing list where the JIRA developers do take part in the customization discussion with other developers. Cheers, Zhen Yueh, Lean
          Hide
          Sherif Mansour added a comment -

          Ive elaborated in a bit more details what I believe the feature request is:
          -------------------------------------------------------
          This is a feature request for the ability to re-name the summary field "Summary" field. The key attributes are:

          • To be able to do this without a restart of the server
          • To be able to do this for each Field Configuration Scheme with a different name (each project can call it something different)

          I am aware that you can do this (http://confluence.atlassian.com/display/JIRA/Customizing+text) however, this work-around has the following limitations/issues:

          • Requires an outage
          • Must apply to all projects

          Business benefit:
          We have had several customers who user Jira for internal workflows to re-name the summary field. Each customer would refer to the summary field, as something different (eg Project Name, Summary, High-level overview....etc...). For those that might not be using Jira just for software development, want to be able to re-name that field to other things (specific to their project)

          Show
          Sherif Mansour added a comment - Ive elaborated in a bit more details what I believe the feature request is: ------------------------------------------------------- This is a feature request for the ability to re-name the summary field "Summary" field. The key attributes are: To be able to do this without a restart of the server To be able to do this for each Field Configuration Scheme with a different name (each project can call it something different) I am aware that you can do this ( http://confluence.atlassian.com/display/JIRA/Customizing+text ) however, this work-around has the following limitations/issues: Requires an outage Must apply to all projects Business benefit: We have had several customers who user Jira for internal workflows to re-name the summary field. Each customer would refer to the summary field, as something different (eg Project Name, Summary, High-level overview....etc...). For those that might not be using Jira just for software development, want to be able to re-name that field to other things (specific to their project)
          Hide
          Thomas Krug added a comment -

          Hi,

          is there a way to preset the summary field with a value (initial action in the workflow or something)?
          Preset the field with date and time or any random text would already help.

          There is a workflow post function "com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction", maybe this can be used in the inital workflow steps somehow?

          Cheers

          Thomas

          Show
          Thomas Krug added a comment - Hi, is there a way to preset the summary field with a value (initial action in the workflow or something)? Preset the field with date and time or any random text would already help. There is a workflow post function "com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction", maybe this can be used in the inital workflow steps somehow? Cheers Thomas
          Hide
          Thomas Krug added a comment -

          Just tested it. I can implement the function only as a post-function within the initial-actions block (which does not override the validator).

          <function type="class">
                        <arg name="field.value">Zeitkorrektur</arg>
                        <arg name="class.name">com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction</arg>
                        <arg name="field.name">summary</arg>
                      </function>
          
          Show
          Thomas Krug added a comment - Just tested it. I can implement the function only as a post-function within the initial-actions block (which does not override the validator). <function type= "class" > <arg name= "field.value" >Zeitkorrektur</arg> <arg name= "class.name" >com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction</arg> <arg name= "field.name" >summary</arg> </function>
          Hide
          Sebastien Forest added a comment - - edited

          Hi,
          I have read and test the workaround, but if I understand it,
          1. I can only do the text customization for one language (english for example). But if a must have at least english and french to support, what can I do ?
          2. I have to redo it every time I upgrade jira (from 3.13 to 3.13.2 as example)
          I'm right or wrong ? Is there any other workaround ?

          Is there any way to recompile a new laguage_default.jar (or any other language file) to replace the actual one ?

          Thanks,
          Sebastien

          Show
          Sebastien Forest added a comment - - edited Hi, I have read and test the workaround, but if I understand it, 1. I can only do the text customization for one language (english for example). But if a must have at least english and french to support, what can I do ? 2. I have to redo it every time I upgrade jira (from 3.13 to 3.13.2 as example) I'm right or wrong ? Is there any other workaround ? Is there any way to recompile a new laguage_default.jar (or any other language file) to replace the actual one ? Thanks, Sebastien

            People

            • Assignee:
              Unassigned
              Reporter:
              Kerstin Klein
            • Votes:
              9 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated: