JIRA plugin enhancement suggestions
CompletedHi Guys
Love the fact that you have created a JIRA plug in, this could be extremely useful for us.
I know it is very early days but I have a few of feature requests please!
1. Be able to filter so that only certain devices are brought back (like Service Level = Production for example)
2. Be able to select multiple devices to be associated with a JIRA ticket
3. Be able to start typing and autocomplete device names
They are the main features that spring to mind which would be needed to make this work for us. It would really help with making Device42 a central part of our tool sets.
-
Hi,
Just a quick note, we added #3, that is autocomplete in v1.0.4 of the plugin: https://marketplace.atlassian.com/plugins/com.device42.atlas.jira.d42jira
We are working on other requests.
Thanks,
Raj
0 -
Hi all,
I'd like to second these enhancements and also add:
- Filter on device type, tags, customer, etc. and combination of those.
- Selecting multiple devices without having to add multiple instances of the d42 field to the Jira screen scheme. I'm not sure if this is a d42 plugin issue or Jira UI issue as I don't recall if Jira has a multi-select UI widget
Thanks,
Aron
0 -
All,
Filters for devices are here: http://blog.device42.com/2015/09/updated-device42-jira-connector-with-ability-to-filter-devices-in-v1-0-8/
Thanks,
Raj
0 -
Currently the device42 JIRA connector plugin supports JIRA upto version 6.4.12.Is there a timeline to support JIRA 7?Also, as per the feature requests on this page, we’d love to have support for the Device42 custom field to be a tag-based feild (rather than a single object field), so that it can support multiple devices being added to a JIRA ticket without requiring us to replicate the field in JIRA screens.0
-
Hi Benjamin,
JIRA 7 support will hit QA towards end of this week and we should have something soon.
We are also looking into multiple device support.
Thanks,
Raj
0 -
Thanks!
0 -
JIRA 7 support has been added: http://blog.device42.com/2015/12/device42-jira-plugin-with-support-for-jira-7/
0 -
Hey Guys, I noticed in JIRA connector 2.0.2 you started using a tag based field, but as per my attached screenshot it only accepts a single entry. Can you convert this into a multi-entry field in version 2.0.3? :D
0 -
I tried the following change to d42field.js but no luck:
JIRA.bind(JIRA.Events.NEW_CONTENT_ADDED, function (e, context, reason) {
if (reason !== JIRA.CONTENT_ADDED_REASON.panelRefreshed) {
$("select.d42-data-field-select").auiSelect2({
multiple: true,
maximumSelectionSize: 10,
allowClear: true,
placeholder: 'Start typing entity name'0 -
Hi Benjamin,
Multiple CI support has not been implemented yet. It is in the works.
Thanks & Regards,
Raj
0 -
IMHO multiple CI support is a MUST HAVE feature. Very often our issues refer to more than one device, asset or part at once. It is very impractical to make multiple D42 fields on a single issue or split the issue into subtasks just for the sake of linking a CI on D42.
0 -
All,
Multiple CIs support is here! http://blog.device42.com/2016/02/multiple-cis-support-for-jira-connector/
Thanks & Regards,
Raj
0 -
Thanks Raj, this is wonderful.
0 -
Do you have plans to backport to Jira 6? Currently is available only for Jira 7.
0 -
Stefano,
Yes, we will be backporting to JIRA 6 as well.
Thanks,
Raj
0 -
That's good news :)
Stefano
0 -
JIRA 6 support is here: http://blog.device42.com/2016/03/per-project-ci-settings-in-jira-connector-v2-2-2-for-device42-cmdb/
0
Please sign in to leave a comment.
Comments
17 comments