TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
RE: best practices - JIRA fields for the docs team ?
Subject:RE: best practices - JIRA fields for the docs team ? From:Rebecca Officer <Rebecca -dot- Officer -at- alliedtelesis -dot- co -dot- nz> To:Robert Lauriston <robert -at- lauriston -dot- com>, TechWR-L <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 24 Dec 2014 01:12:42 +0000
> If the UI field is initially "no" and at some later date you change it to "yes," does the docs issue still get created automatically?
I think so, and I seriously hope so. I've emailed our JIRA admin to ask, but he's off for Christmas and not back till mid-Jan.
Unfortunately, you're right that JIRA OnDemand can't run that plugin. I find it amazing how few plugins OnDemand runs.
Cheers and Merry Christmas!
Rebecca
-----Original Message-----
From: techwr-l-bounces+rebecca -dot- officer=alliedtelesis -dot- co -dot- nz -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+rebecca -dot- officer=alliedtelesis -dot- co -dot- nz -at- lists -dot- techwr-l -dot- com] On Behalf Of Robert Lauriston
Sent: Tuesday, 23 December 2014 5:52 a.m.
To: TechWR-L
Subject: Re: best practices - JIRA fields for the docs team ?
That's a nice trick. If the UI field is initially "no" and at some later date you change it to "yes," does the docs issue still get created automatically?
Probably irrelevant for me since we use JIRA OnDemand and it can't run most plugins.
On Sun, Dec 21, 2014 at 3:18 PM, Rebecca Officer <Rebecca -dot- Officer -at- alliedtelesis -dot- co -dot- nz> wrote:
> We get a separate DOCs issue for each docs-affecting software issue, automatically. Software issues have a field that asks whether they changed the user interface behaviour. If the software engineer says yes, JIRA automatically creates a Docs issue and links it to the software issue. That way you don't have to worry about the engineers remembering to make a Docs issue. This is done through a free JIRA plugin called Groovy Script Runner.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1pJ4zPa
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1pJ4zPa
