PJ Wysota Expert

1. Firstly - if You create a form through the portal - it should also assign CRT to the issue. However - if You create issue through JIRA backend - it won't (at least automatically). If there are any issues with assigning CRT to issue for specific user - I would start with checking Permissions (that You are on Customers…

There is quite good documentation on JQL: https://confluence.atlassian.com/servicedeskserver/advanced-searching-939937012.html 1. Fields - firstly look at JQL construction: First - FIELD, then OPERATOR, then VALUE Means that your case would look like: Assignee [OPERATOR] [VALUE] 2. Operator - as you are looking for current…

The answer is simple, but execution might be a bit though: You need to upgrade source instance JIRA. https://confluence.atlassian.com/adminjiraserver/upgrading-jira-applications-938846936.html It might be harsh, especially if version difference between source and target instances is high (once I had to do migration from…

FIrst things first: 1. I wouldn't go for REPLACING objects already in Insight inventory - due to regardless of other data corrected - when replacing (A.K.A. Deleting old object and creating new) You will drop all references between object and JIRA tickets (every imported object is given not only a key but also UID -…

ANd here we go with off-top off-top: promised riddle - what does the picture say, and what was a note I skipped on Darth Vader above?

I love it... And it is sooo.... Nah, won't write it down - it will be a riddle in next post ;-)

There is System field Required Participants - which allows to add different Customers (of course you need to manage permissions - both global and project level one) Another option is to use Organizations (but then it is fixed against all Customers within same organization).

WIth standard Insight operations - nope. However there is a trick allowing that with postfunction. :-) Revealing a secret behind 2nd part of Valiantys blog posts on Insight mastering: if You use Create Insight Object from issue - you can pick the fields in JIRA ticket to have Insight object attributes assigned. If any of…

I do not think it will be possible with standard JIRA filter macro. It is developed by Atlassian, and usually any Custom field listed is just showing values (not mentioning that for insight You will get "DB like" value, combining name with Insight Key. Insight for CONFLUENCE - well, it is focusing on Insight objects,…

it did... However, as I mentioned - it is slightly different and to show it off - we still need to depersonalise that. But point taken and in predictable future (few weeks) you will see it. :-)

No prob.

oh yes... 

1. No floating licenses 2. Yes, you can reassign license, but then you need to reassign it back once person is getting back You do that by changing users in group(s) which are assigned to Application access

ok, "usuario" in surfaces should be insight reference to "LDAP whatever" object type. then pick the attribute in LDAP that will be the same for both imports, if that is username - fine, if that is e.g. e-mail - let it be. Than firstly import Users Then set up Surfaces import with "Usuario" IQL mapping like ATTRIBUTE (user…

OK, Hardware ID is just exemplary attribute for mapping. In case you mention I would: 1. Firstly get list of models in Insight as separate objects 2. On actual Mobiles attribute I would create reference to Object Type referring to models 3. The same - on actual Mobiles Object Type - an attribute to JIRA users OR Insight…

Not at hand - I would need to do that and test. And this is actually something I wouldn't have time for within next few days.

You mean built in automation in JIRA SD? not really. rather Automation for JIRA add-on.

ANd there you go: https://blog.valiantys.com/en/expert-tips/insight-for-jira

if objects are updated (not deleted and created) attributes created internally in Insight will remain. :-)

there is :)

Sure - script runner or any competitor (e.g. automation for JIRA) would do that. But it won't relate Reporter to the chosen location. It will only allow to set assignee on the scheme: IF Location = XYZ THEN Assign to ABC

Just answered another one :-)

In this meaning - nope. What we are using is a workaround: - separate Object Type called CI category - objects may (but don't have to) be in line with Object types (in our case they are not - there are 6 main categories, where we have around 60 different object types - other object held attribute - reference to which…

EDIT - confirmed - it will be in 2h time.

Hi there, I hope to give you proper answer in few hours max. :-) The point is Insight imports are exactly the topic for the blog post I did for my company. Should be published today, but I cannot be ahead of our Marketing team :-)

1. Yes, it is possible: - make respective field in JIRA custom fields - add it to Create screen representing Issue type that Portal CRT is mapped into - add a field in CRT setup in JSD Project settings 2. IMHO with radiobuttions UX will suck. Select list would be the latest. Then - if you want to make further actions based…

1. Installing script runner upfront should solve issue with formatting the scripts. Still you will face the one with mismatched UIDs. 2. As mentioned above: - I would check the import file for number of issues - I would check Permission and security schemes if they match - if these won't give you answers - I would check…

then I would suggest reporting it to Atlassian support.

How about reindex after changes?

1) Known issue - there are quite a few issues with add-ons when migrating, and one of these is Script Runner - not only the format, but also UIDs can be mismatched, so the bast practice is to rewrite the scripts (copy-paste and match the UIDs again). ANd yup - Script runner should be installed upfront. 2) First idea:…