JIRA integration for Workflow Tasks?

Is there anything on the RoadMap for integrating Workflow Tasks with Jira?

We're use Jira for product support and Confluence with the Adhoc workflow plugin for the documentation, so currently, there are 2 "repo's" with tasks.

Would be great if the Workflow tasks could end up in Jira as well.

P.
7 people have
this question
+1
Reply
  • It's on the roadmap.

    We welcome ideas on how people would like to see this implemented.

    Roberto
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Hi Roberto,

    It would be great if we can have this implemented through a WF Macro to create a JIRA task from within AD Hooc WF, passing parameters from the active page metadata and page related info.

    Any dates as to when this new feature might be available?

    many thanks
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Is there any progress on this item? If not, is it still on the roadmap, somewhere in the foreseeable future?

    As to you question how this ought to work: just a couple of idea's form the top of my head:
    - bind a space in Confluence to a project in Jira
    - tasks in the Adhoc workflow are issues of a certain type in Jira
    - the issue in Jira has a custom field with a link to the Confluence page on which the task is created in Jira
    - in Jira you have a special "Page picker" element to select a space and page when creating cases from there
    - when creating tasks in Confluence they "just" end up in Jira on the project linked to the space in which the page resides

    I'm sure there are a bunch of pitfalls here and there.

    P
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • We have a scenario where we want to track a project through various stages in Jira and want to use Adhoc Workflow to control documents created at each stage. The integration would need to prevent the Jira issue from progressing until the specified documents had been approved and published at each stage.

    I'm sure there are many more complexities to consider :-)

    Chris
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Miguel (Support Engineer) December 06, 2011 09:34
    Those are all good ideas however there currently has been no progress on integrating Ad hoc Workflows with JIRA.

    It is still on the roadmap as we are always looking at ways to improve our product such as adding JIRA integration. That said, we have no firm plans as to when or even if it will be done. I wish I could be more specific but as things are always changing, it is hard to pin down when we might look at adding a particular feature.

    Thanks,
    Miguel
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Just following up on this thread... Has there been any developments in this area in the last year? In-particular, is there a way of creating a JIRA task (or tasks etc) when kicking-off a review/workflow?

    Cheers
    Garry
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Miguel (Support Engineer) November 14, 2013 01:58
    Hi All,

    We do have an open issue in our system for this feature as we do with many of the feature suggestions we have received over the years.

    While we would love to implement everyone's ideas, unfortunately we receive far more good feature suggestions than we have time to implement. As a result many of them end up not getting implemented.

    That said for this particular idea, it has come up a number of times over the years for consideration, however with Atlassian starting to push more into tasks such as the existing Confluence Workbox Tasks, it appears that this feature may become built into to Confluence/Jira sometime in the future.

    As Ad hoc Workflows already integrates into Confluence tasks as much as is possible, if/when Atlassian adds this functionality, this ability should be available out of the box.

    Thanks,
    Miguel
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • With the recent integration between JIRA and Confluence, there are a couple of Ad-Hoc WF improvements that would be handy.

    New Trigger events (primary parameter would be IssueKey, others depend on event):
    - issuestatus (simply checks if the current issue status=, and triggers accordingly)
    - issuestatuschanged (would also want to be able to specify triggering on a specific status, e.g. "resolved", "closed", or a custom status)
    - issueassignee (simply checks if the current assignee=, and triggers accordingly)
    - issueassigneechanged (would also want to be able to specify triggering on change to a specific assignee)
    - issueupdated (could be one event using parameter options, or broken into different events; things like "commented on", " commented on", an attachment is added, "summary" is changed, one of the fields are changed, work is logged, etc.)

    New Workflow Macros:
    - updateissue: [issuekey]/[JQL] | [status] | [field] | [comment]
    * issuekey OR JQL: either specify a single IssueKey OR insert JQL to perform query for all issues matching JQL, other parameters are applied according to the IssueKey or any issue matching the JQL criteria
    * field: catch-all for any field defined for an issue, such as [summary] | [description] | [assignee] | [reporter] | [additional users to be notified] | custom fields
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned

  • Miguel (Support Engineer) June 21, 2014 04:30
    Hi Robert,

    While Ad hoc Workflows can be used somewhat as an automation tool, it's designed more for approving and workflowing page content, so I'm not sure if that fits in with the product or not. I suppose it could be available as a separate add-on, adding functionality to Ad hoc Workflows, directly to Confluence, or even directly to JIRA.

    We are certainly open to adding new functionality, but my boss is big on use cases, so it would help a lot if you could explain how things like that would be useful to you. Our actions are somewhat limited so if you could also include what kind of actions you might want for each trigger type.

    Thanks,
    Miguel
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. kidding, amused, unsure, silly happy, confident, thankful, excited sad, anxious, confused, frustrated indifferent, undecided, unconcerned