Answers.Body: <p>The "Inherit Title" plugin might work for you but you will have to test it for your needs. It hides the title field and then uses the content of other fields in the entry to automatically generate the title for you.</p>
  
  <p><a href="https://github.com/rkingon/Craft-Plugin--Inherit-Title/" rel="nofollow">https://github.com/rkingon/Craft-Plugin--Inherit-Title/</a></p>
  
  <p>From the read.me:</p>
  
  <p>Say you have a "firstName" and "lastName" field, and you would like the Title to auto populate with "firstName lastName" you could use: "{{firstName}} {{lastName}}" as your settings configuration.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T09:50:41.670Z
Answers.Text: The option to use an auto-generated title is now a native option. It sounds like it has all the same options, but specifically the issue is with using Entry type content within the field.
Answers.UserDisplayName: Joel Bradbury
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T10:06:18.207Z
Answers.Text: Hey, thanks for that, I had no idea. Brandon and the crew are on such a rapid development cycle, it is hard to keep up with all the new features (not a bad problem to have) :)
Answers.UserDisplayName: Steve Adams
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T09:46:52.627Z
Answers.LastActivityDate: 2014-06-12T09:46:52.627Z
Answers.UserDisplayName: Steve Adams
Answers.Body: <p>You can access the Software entry’s title exactly the same way you would in your front-end templates: <code>software.first.title</code>. The only difference is the single-brace tags syntax, which you don’t even <em>have</em> to use if you don’t want to. Both of these are identical:</p>
  
  <ul>
  <li><code>{software.first.title}</code></li>
  <li><code>{{ object.software.first.title }}</code></li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-11T14:32:32.610Z
Answers.Text: How would you loop through a category field if it has multiple selections in a tree and you want them all to be in a title? No syntax I try works.
Answers.UserDisplayName: Alan Miller
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-11T16:45:00.900Z
Answers.Text: @AlanMiller Not sure I’m following. Probably worth posting a new question.
Answers.UserDisplayName: Brandon Kelly
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-09-11T17:22:32.673Z
Answers.Text: I asked my question here, thanks! [Multiple category output in auto generated](https://craftcms.stackexchange.com/questions/2493/multiple-category-output-in-auto-generated-entry-title)
Answers.UserDisplayName: Alan Miller
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-06-12T12:19:01.793Z
Answers.LastActivityDate: 2014-06-12T12:19:01.793Z
Answers.UserDisplayName: Brandon Kelly
Body: <p>How would you setup a section's entry type to auto-generate the titles based on the title (or slug) of another entry?</p>
  
  <p>For example, we have a <strong>Software</strong> section with entries. We also have a <strong>Releases</strong> section. Each release entry has a related software entry, along with a versionNumber text field. </p>
  
  <p>Ideally each release's title would be of the form : </p>
  
  <p>{software.title} {versionNumber}</p>
  
  <p>Where {software.title} is the title from associated entry.</p>
  
  <p><img src="https://i.sstatic.net/baS7i.png" alt="Title Format input example"></p>
  
  <p>We've looked at all sorts of combinations to get that value out, but any usage seems to either be ignored or throw an error on publish.</p>
  
Tags: <titles><auto-generate>
Title: Using auto-generated titles against entry field type values
ThreadText: # Using auto-generated titles against entry field type values
  
  (Asked by: username_0 on 2014-06-12)
  
  How would you setup a section's entry type to auto-generate the titles based on the title (or slug) of another entry?
  
  For example, we have a **Software** section with entries. We also have a **Releases** section. Each release entry has a related software entry, along with a versionNumber text field.
  
  Ideally each release's title would be of the form :
  
  {software.title} {versionNumber}
  
  Where {software.title} is the title from associated entry.
  
  ![Title Format input example](https://i.sstatic.net/baS7i.png)
  
  We've looked at all sorts of combinations to get that value out, but any usage seems to either be ignored or throw an error on publish.
  
  **Tags:** titles, auto-generate
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_2 on 2014-06-12. Score: 10 | Accepted answer
  
  You can access the Software entry’s title exactly the same way you would in your front-end templates: `software.first.title`. The only difference is the single-brace tags syntax, which you don’t even *have* to use if you don’t want to. Both of these are identical:
  
  * `{software.first.title}`
  * `{{ object.software.first.title }}`
  
  > **Comments:**
  > **username_3**: How would you loop through a category field if it has multiple selections in a tree and you want them all to be in a title? No syntax I try works.  
  > **username_2**: @username_3 Not sure I’m following. Probably worth posting a new question.  
  > **username_3**: I asked my question here, thanks! [Multiple category output in auto generated](https://craftcms.stackexchange.com/questions/2493/multiple-category-output-in-auto-generated-entry-title)  
  
  ---
  
  ### Answer by username_1 on 2014-06-12. Score: 0
  
  The "Inherit Title" plugin might work for you but you will have to test it for your needs. It hides the title field and then uses the content of other fields in the entry to automatically generate the title for you.
  
  <https://github.com/rkingon/Craft-Plugin--Inherit-Title/>
  
  From the read.me:
  
  Say you have a "firstName" and "lastName" field, and you would like the Title to auto populate with "firstName lastName" you could use: "{{firstName}} {{lastName}}" as your settings configuration.
  
  > **Comments:**
  > **username_0**: The option to use an auto-generated title is now a native option. It sounds like it has all the same options, but specifically the issue is with using Entry type content within the field.  
  > **username_1**: Hey, thanks for that, I had no idea. username_2 and the crew are on such a rapid development cycle, it is hard to keep up with all the new features (not a bad problem to have) :)  
  
  ---
  
  