Hi All,

Our Jcreate app adds the ability to map Confluence table columns to Jira issue fields, you really should give it a try!

Paz Methoda

I would use it for Requirements gathering template for specific set of fields to populate into an issues. Probably ones like, Labels, Priority. I would also think it make a lot of sense for the Jira ticket to automatically link back to the source product requirement table/page in confluence.

HI, 

We have built an addon that provides the ability to have full issue screen and configuration in Confluence

see: https://marketplace.atlassian.com/apps/1224226/jcreate?hosting=server&tab=overview

Best regards,

Yaniv

This would greatly increase integration benefits of Jira & Confluence in our company. For example, when we do meeting notes internally or with suppliers we make our meeting notes in Confluence. Then, the idea is to make a table in the meeting notes which describes needed actions (example: supplier needs to look into a problem, an internal team needs to look into a user story...). The issues would be made straight from Confluence so they are directly integrated with Jira and our Scrum/Kanban Boards for our teams. This reduces admin for status follow-up greatly since the Confluence report will just automatically update the Jira issue status in the meeting report for our next meeting.

We have many teams in a single project, each with their own Boards. Our team Boards show only issues relevant to a certain team by filtering on some standard & custom fields. Our suppliers also have access to JIRA, so issues related to them are mapped using different fields. Also, there's a high degree of classification needed because we have many many issues. For that we use Epic Links, labels or Components for example.

Therefore the current functionality to make Jira issues from Confluence is too limited in our company. We would need the option to map more columns from a table to fields (for example a column "labels" or "Components" or any custom field). Some kind of templates/applied fields would also help, since within each Confluence page we usually have a lot of fields that should be the same for all the created tasks in that page.

Adding at least some Jira system fields would be highly desirable. While Resolution field is not really applicable here, Labels field should be added at minimum. 

Interesting if the feature would include date fields. As Atlassian showcase is to start project initiation (documentation) from Confluence, it would make sense that at least all date fields should be supported on creation of Jira issues. For example start and end date so you can create multiple tasks for use in planning apps like Big Picture, Advanced Roadmaps etc.

Should we clone and reopen this issue? I don't believe something I've been watching and people are actively voting on should be 'not considered' without some type of explanation from the PO/PM....

 
jmillman made changes - 01/Feb/2018 3:39 PM

PM Reviewed		02/Feb/2018
Status	Reviewing [ 11773 ]	Not Being Considered [ 11776 ]

Hi community,

I hope you don't mind this intrusion, but I encourage you to check out our new app.
IssueCreate works as many of you described above. It is able to create multiple issues from a table with almost any type of fields.
You can find more information on the marketplace, or on the documentation site.
 

Best regards

Hey!  I voteing on this   

Hello Atlassian, 

Its more than 6 years. how much time you need to develop this basic and imp functionality?

Regards,

Abhi