Late to the game here, but I concur with Narayan's suggestion - capture the details in issues, then make this an issue report grouped by project. That will reduce the number of fields you have to create, and is going to enable some quality reporting down the road. Filtering on criteria like OW/RT or Fare Segment Name will be really easy, when that data exists only in one field each. If you had fields "Segment 1 OW/RT" and "Segment 2 OW/RT", all the way up to 10 (or more!) permutations, you'd be cursing Workfront when it comes time to report on this data.
You could do this with task OR issue forms; but I find issues more flexible to work with. The exception would be if each segment needs to have its own set of sub-tasks, but that doesn't sound like the case here.
Good luck! William English T-Mobile
If you like my content, please take a moment to view and vote on my Idea Requests: https://tinyurl.com/4rbpr7hf