diff -r 71643a839c80 roundup/cgi/actions.py
--- a/roundup/cgi/actions.py	Thu Jul 14 22:03:48 2016 -0400
+++ b/roundup/cgi/actions.py	Sat Jul 16 21:16:31 2016 -0400
@@ -726,7 +726,13 @@
         # commit now that all the tricky stuff is done
         self.db.commit()
 
-        # redirect to the new item's page
+        # Allow an option to stay on the page to create new things
+        if '__redirect_to' in self.form:
+            print "found stay new %r"%self.form['__redirect_to'].value
+            raise exceptions.Redirect('%s&@ok_message=%s'%(
+                self.form['__redirect_to'].value, urllib_.quote(messages)))
+
+        # otherwise redirect to the new item's page
         raise exceptions.Redirect('%s%s%s?@ok_message=%s&@template=%s' % (
             self.base, self.classname, self.nodeid, urllib_.quote(messages),
             urllib_.quote(self.template)))
diff -r 71643a839c80 share/roundup/templates/classic/html/keyword.item.html
--- a/share/roundup/templates/classic/html/keyword.item.html	Thu Jul 14 22:03:48 2016 -0400
+++ b/share/roundup/templates/classic/html/keyword.item.html	Sat Jul 16 21:16:31 2016 -0400
@@ -36,6 +36,20 @@
   <tr>
    <th i18n:translate="">Keyword</th>
    <td tal:content="structure context/name/field">name</td>
+   <td tal:condition="not:context/id">
+     <tal:comment tal:replace="nothing">
+       If we get here and do not have an id, we are creating a new
+       keyword. It would be nice to provide some mechanism to
+       determine the preferred state of the "Continue adding keywords"
+       checkbox. By default I have it enabled.
+     </tal:comment>
+     <input type="checkbox" id="continue_new_keyword"
+	    name="__redirect_to"
+	    tal:attributes="value
+			    string:${request/base}${request/env/PATH_INFO}?@template=item;
+			    checked python:True" />
+     <label for="continue_new_keyword" i18n:translate="">Continue adding keywords.</label>
+   </td>
   </tr>
 
   <tr>