Create Multiple Issues from One Paragraph (Multi-Line) Field
Asked by Alex Young:

Hey community!

I got a feature request that I am not sure how (if at all) to do it.

Summary and Context {#toc-hId--385724560}
-----------------------------------------

I am an Atlassian admin for a small, membership-based non-profit. Our central office provides services to our chapters, which members belong. Our central office uses JSM and the Help Center to collect requests and reports from chapters. I have a feature request from our membership services unit in our central office which would necessitate automatically creating multiple issues from data provided in a single paragraph custom field on a request received from our help center.

Use Case {#toc-hId-2101788273}
------------------------------

It is natural that members of our chapters are ending or changing their membership status with our organization. Chapters would submit a request form and in that form list the names and emails in a single paragraph field, **one person on each line** . We want to use automation to create **one** **task** issue for **each line** of the value in the paragraph field for our membership services team to reach out to each member provided.

![Drawing6.png](https://community.atlassian.com/t5/image/serverpage/image-id/305268i29AD826FC98887AD/image-size/large?v=v2&px=999 "Drawing6.png")

Question {#toc-hId-294333810}
-----------------------------

I am not aware of a way to parse out the data provided in the fields and then generate issues based on that data. Any guidance, recommendations, or alternatives are appreciated. We would like to avoid marketplace apps, but we are open.

Thanks!


Answers:
author: Hariharan Iyer
body: Hi [@Alex Young](/t5/user/viewprofilepage/user-id/5399951) ,

You can do this using Automation Rules (under Project Settings -\> Automation) in JSM. The rule you would need to create would be similar to below

![Screenshot 2024-02-09 at 10.07.18?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/305366i13D8104A2CB040E6/image-size/large?v=v2&px=999 "Screenshot 2024-02-09 at 10.07.18?AM.png")

Let's walk through the steps in this rule.

![Screenshot 2024-02-09 at 10.07.46?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/305367i66B8CC56CEA840A3/image-size/large?v=v2&px=999 "Screenshot 2024-02-09 at 10.07.46?AM.png")

In JSMPROJ, assuming the list of users and emails is populated in the description field, the "For each" step would be as above. Please adjust it according to your field name.

The next step is pretty self-explanatory - we're skipping empty lines since we can't create tickets for those.

The last step would be like this

![Screenshot 2024-02-09 at 10.08.04?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/305369i89DEFB6489197F4E/image-size/large?v=v2&px=999 "Screenshot 2024-02-09 at 10.08.04?AM.png")

Select the Project (PROJ in your case I believe) and Issue Type as per your requirements. Enter the summary value as it's mandatory. The things to note here are:

1. The username can be fetched using *{{userDetail.split(",").first}}*

2. The email is fetched using *{{userDetail.split(",").last}}*

3. Adjust the separator as per your requirement

4. In the "Additional Fields" textbox, we've provided a json to set the two fields you need. Please change the field names as per your requirements. You can also select those fields from the "Choose fields to set" option.

Hope that helps!

comments: author: Alex Young
body: [@Hariharan Iyer](/t5/user/viewprofilepage/user-id/5124435) this is exactly what I needed! Thank you so much!


Tags: automation

cloud

jira-service-management

jira-service-management-cloud