PJ Wysota Expert

If they are customer, they will be able to clock, Open issue and comment inside JIRA. But nothing like fancy RO vwrsion od SS project view.

The same on server. So this is one thing, another is notifications scheme. :-)

I would check two things: notifications scheme related to project and Customer notifications in JIRA SD project settings in JSD there are 2 types of notifications https://confluence.atlassian.com/servicedeskcloud/configuring-service-desk-notifications-732528936.html

`It is not clear if You use JIRA Core/Software or JIRA Service Desk. For first - Joe above is right however it is not as simple, as issues might not be visible, but Issue type will be on creation screen. With Jira SD however - the only answer now is Extension for JIRA SD by Divinity - with CRT Security/Visibility options:…

Cześć Marku <switch to EN mode ON> It is not possible this way. The queues are native functionalities of JIRA SD and therefore use of queues is strictly related to LICENSED JIRA SD agents. 1. However there is a possible workaround: JIRA SD projects allow to have RO access to view issues for non-agents (visibility of…

Apologize denial, but No, thank you, no. And apart from any freelancers (I am not sure if Community is the best approach to address them), I would discourage anyone to do so. And here we go with rationale behind it: 1. JIRA Service Desk offers built in SD Portal for such purpose, plus SLA module 2. If not JIRA SD - JIRA…

1. in this format - not possible with standard JIRA SD capabilities. 2. eazyBI for JIRA Cloud would help: https://marketplace.atlassian.com/apps/1211508/eazybi-reports-and-charts-for-jira-cloud?hosting=cloud&tab=overview If you don't want to use eazyBI: 1. each of columns would require separate JQL 2. You will not be able…

Confluence 5.3 Admin Guide PDF Site Backup and Restore paragraph.

You can. Application links work fine between JIRA Server and Confluence Cloud, however there will be few minor issues You may expect (due to technology): - any corporate SSO will not work for Cloud services - You would need to manage users for Cloud separately - in Cloud instance - they might be the same as JIRA ones, but…

They do work. So if You would setup your field with: Object Type mapping to apps, and Filter Issue Scope referenced either to Issue type or Customer Request Type (in JIRA SD) it would work. However You would need to keep attribute naming convention exactly the same as Issue Types or Customer Request Types. Any alteration…

Oh, nice You post the whole structure. 1. The point is You are not going 2 levels down the hatch, as You stated previously, but a bit more Order Reports 5.2.1 -> Order System 6.5.2 (level 1) -> Order System (level 2) -> Applications (level 3) So You need IQL with 3 levels depth query. Then - as stated in linked topic: for…

Thank You!

OK, so it is more clear now. You mismatching some use cases. But to make it faster - here are solutions: Field Application - to be picked by User - it should be Insight CF with Filter Issue Scope - it should pint out to "ObjectType = Application" Then Your hidden field - if this is JIRA CF (text/Select) - use post function…

OK, I might know what is all about, but to not mislead You I would need some more details: 1. Hidden Field - what kind is it? Insight, or JIRA Field (Text, Select etc.)? 2. Do you have ObjectType in Insight called "Type" or "Incident"? 3. Have you tested variable with CF name instead of custom field_XXXXX? 4. Have You…

Nope. If You are using flat attributes (Text, selects etc.) Obviously you will be limited to first level of references, as there are no more levels. But example above shows exactly the case to retrieve object at 2nd level. Then modifying the query (using different attribute than Key) you might retrieve other value. And if…

I looked at it our demo environments - of course this is one use case but: 1. Insight fields - as You see - I use 2nd level Ref field to not mismatch it: 2. This is object DNL1001 with some attributes refering to other objects: 3. A you can see we have a manufacturer here (Dell) but also in Model (as a attribute of model)…

As You are not referring to this, I cannot be sure what references You use: outbound or inbound. And there is a difference - look at this topic: https://community.atlassian.com/t5/Jira-questions/Insight-referenced-field-indirect-referenced-object-2-tier/qaq-p/884409 where I posted some examples. Then with variable to Field…

OK, indeed one lack of IQL is lack of auto-suggestions - both in INSIGHT directly, in IQL in JQL in JIRA and in IQL in Confluence macro. So - NO SOLUTION :-) But workaround I use is to test IQL initially in Insight using either search functionalities or IQL scoping for Insight Field in JIRA ticket.

Simple case: Insight objects are indexed in JIRA/JQL as "OBJECT_LABEL (INSIGHT_KEY)" , where Key is taken from schema prefix and consecutive object number, so JQL for any purpose (including SLA) should look like: "issuetype = Incident and mSE_Application = RSS(KEY)"

There are two ways of doing so: 1. Direct JIRA DIrectory users/groups (User/Group attribute type in Insight Objects) Pros and Cons: + direct relation to JIRA users/groups + simpler IQL queries for automations, Post functions etc. - no reference showed in Insight Digrams - no user attributes - like phone, contact details…

Well, there is a way: 1. You need to use Insight 5.4+ (older versions do not support it), and instead of referenced fields (although it might work with Referenced Fields, as I did not test that - since 5.4 I do not use Ref. Fields at all) 2. For outbound references You would use Issue Scope/Assign Scope with IQL syntax…

Good story, bro! I still remember our first talks on Issue Templates prior to development. Why We (as I was part of Allegro then) came to Intense with request, first set of functional and non-functional requirements, tests of first Alpha, Beta versions and all that stuff. And I still consider it as one of game changers in…

Apart from docs... (but I also suggest reviewing quite few of them) - apart from above also versions release notes, scaling JIRA docs (https://confluence.atlassian.com/enterprise/scaling-jira-7-7-943526476.html) etc.plus this one: https://confluence.atlassian.com/doc/performance-tuning-130289.html 1. Volumetric - of course…

Do you are doing EXACTLY what we have discuss with Riada - sequencing import. SW objects go first. Then you create PC with referencje to just create, but already EXISTING SW objects. :)

And you run JIRA on Apache/Tomcat or IIS/Tomcat? If everything else is running, I would check these as well.

Try to check running services - if there are no duplicated JIRA/Catalina service. If there are it might be the cause. Quick fix attempt - kill java process in Task manager , and then start JIRA service from power shell. And then review config if everything is OK.

1. For Portal access only - You don't need licenses. 2. The same would be for Customers with approval But You need to setup Customer Portal Access in Project configuration

Well, You will not. :-) Here is a post from me, that could help you (subsequent imports need to be done), but as discussed with RIada - there are currently no options to CREATE referenced objects on imports - the only upgrade of this functionality they think of currently is maybe some sequencing imports to allow creating…

Untill your license is valid it should be. However with Eval license expired - I truly don't know. However - if backup-restore is not an option.... ...then I would say only manual migration (re-doing all configs manually + migrating one project after another via csv files). It is time consuming, but still can be done.

Hi there... First of all I would avoid if possible to have both on the same machine... There is a variety of reasons (multiple tomcats, apps availability, JVM resource consumption, etc.) to have JIRA and Confluence separated, and of course You CAN have them on the same server, but if possible - healthier would be separate…