There's two totally unrelated questions here.
Xporter is for getting JIRA issues out into document formats
For conditional assigns, you might need to expand on the question. The easy answer is "use component leads" as you can automatically assign issues to them. But I'm not sure where the tech writer might come in (especially as you can only have one assignee for an issue)
I apologize for combining the questions in one ticket... this is my first time using the forum...
To expand on my question about conditional assigns... After a ticket has been completed by the developer and tested by QA, it is assigned to documentation. I would like the ticket to be automatically assigned to a person in documentation based on the component field. Is that possible?
No problem, your clarification was great :-) You can't do that second assignment with Jira off-the-shelf. You need a post-function that can look at the component and understand who should be assigned in the QA step. I'm not aware of any in the standard plugins I usually recommend - the closest you can get with them is to have an extra user-picker field for "QA person" and use one of their copy functions to take whatever the users have entered and assign that user on the transition. But I suspect you probably want to go the whole hog and use the script runner to do a big "case" statement on the QA user (unless you want to write your own plugin of course)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs