Ravi Sagar _Sparxsys_ Expert

Hi @Anders Honore Yes it is possible but why not create a linked dev issue from JSD to Jira Software? You can surely update the status of your JSD ticket to a specific status like "For Dev" for reporting purpose and letting your customers know about it as well (if you want to) but at the same time create a linked issue for…

Post a screenshot of your Project Settings | Screens with expanded screen scheme as Jack showed above. Let us take a look. Issue Type Screen Schemes are a bit tricky. * Issue operations (create/edit/view) are mapped to Screen and this mapping is called as "Screen Scheme" * The "Screen Scheme" is then mapped to the Issue…

Hi @Jai_Nirwan Downgrade your SR4J and try the 5.5.9 version from this page. @Max Berger What is your Jir and SR4J version? Try the 5.5.x version which is compatible with your version of Jira. Ravi

Hi @Charles Focant No it only searches the KB articles not Jira issues/requests. However if a request is shared by customers by adding other people/organisation as participants then it is somewhat possible (by going to Requests | All requests link on top right) but it is not through the search feature. Usually when an…

@Craig Baillie Definitely in this case 1 project with multiple releases makes sense. This why fix versions are there in Jira. I think it is more of a case of training the users about filters, issue navigator, dashboards and reports. Since you mentioned agile. Also educating them on using epics, labels, boards with relevant…

Good to know. Have a nice day.

Your Sales Collateral field name is different. Change it in the code.

Hi @Angelin Time to first response - when the customers are contacted by an agent with an acknowledgement of the ticket. It is important to assure that their tickets are being looked at. It is usually short - less than few hours. Time to resolution - actual time it takes to resolve the ticket and provide solution. It can…

I enabled the dark feature and the behaviour still works for me. So not sure why it is not working for you. 

Hi @[deleted] JSD acts like another layer on top of Jira. Fields you added are added in Jira which is step 1. If you try to create issue from within Jira you should be able to see those fields but not on the portal. Step 2 would be to add those newly added fields in your request form (which are mapped to request types).…

Hi @Steve H Before importing issues in JSD store the old issue key (SUGAR-1234) in a custom field and then you will have to use a custom mail handler app like JEMH. So if any mail coming with old issue keys can be searched internally before creating a new issue. ScriptRunner for Jira can potentially do that as well. Here…

What is the exact type of Sales Collateral field?

Hi @Teja Try this. Add both the fields with the following code respectively. Sales Collateral def salescolValue = getFieldById(getFieldChanged()).getValue() def salescolOwnValue = getFieldByName("Sales Collateral Owner").getValue() def salescolCom = getFieldByName("Sales Collateral Completed") if (…

Check the ID or Class of your field using Inspect option in your browser and use that in the code.

Hi @Benjamin Martin You would need an add-on for this. Using ScriptRunner you can create a new scripted field that will generate the clickable url for you (with JQL for searching). Use the new field on view screen and the original field on create/view screen. Ravi

Ok try this. <style type="text/css"> textarea#customfield_12702 { height: 200px; } </style> Find the custom field id of your field and replace in the code above.

Hi mani@123 Do you mean the visual height or number of characters the field can take? You can try inserting some custom CSS in the banner to increase the height of that field to make it visually bigger. Ravi

Check if you see any error in your browser console, also try in a different browser.

A bit strange usually the icon appears after enabling the dark feature and by adding the line. Which you did. What is your Jira and ScriptRunner version?

Hi @siva kedari veerla It can be done by writing custom JavaScript (in custom field description) or using ScriptRunner Behaviours, check this example. Ravi

Hi @Jai_Nirwan Did you enable the dark features? Ravi

Hi @Merve Nur Bas They are free (I think. I never paid). Sign up and you will receive invite link. Ravi

Hi @[deleted] What is your end goal? Do you want to do something like SAFe with different levels? Just wondering why you need to nest epics, is it for grouping them or creating hierarchies? Ravi

Hi @Mark Ryel Alonzo Sumagaysay Use Issue Navigator with the query like this and add the field in the column as well. "Custom Field" Name is not Empty It will return a list of all the issues where the custom field is being used. It might not be on a screen but may be it was used in the past or it could be on a transition…

Hi @[deleted] Try filtering the parents and add a column called Sub-Tasks. Ravi

Hi @Certus Port Automation If your customers are already part of an organisation then you can define these SLAs using JQL with a query on organisations. You can find some examples here. Ravi

Hi @Charan Nagaraja It is quite common question. There are already lot of similar posts on the community on this topic. If you are willing to do this outside Jira where you can control the frequency then it is quite simple task using REST API. You do that using a simple shell script (added to crontab) with a curl command…

Hi @Teja That's really good so far. I think you are close. How did you combine the 2 conditions together? Share the code, let us see why it is not working. Ravi

Hi @Per Arne Føllesdal If you just want to have a count of issues then try using a pie chart gadget based on component field. You can also use Two Dimensional Filter Statistics or Issue Statistics. Ravi

Hello @Teja Take a look at this example here. It will probably give you good idea on how to achieve this. Let me know. Ravi