Comments
-
Hi @Martina I am not sure if I understood your requirements clearly. Do you want to display all the versions of the issue on the card? If you want to display the fix version then you can go to Board | Configure | Card layout and add additional fields (upto 3) on the card. Ravi
-
Hi @Tarak Ram Jira Service Desk is the service desk solution for Jira. It comes with a customer portal for every project where customers can raise tickets. There is no restriction on number of customers. Jira Service Desk has lot of standard features of a typical service desk like request types, queues, SLAs, agents,…
-
I am glad it was useful. Thanks.
-
Hi @Marcela Junyent Where are you running this script? and can you share the link from where you copied it? Thanks, Ravi
-
Hi @Kushal Arora The webhooks triggered from workflow transitions are different from other events like issue created, updated or comment version released. The order you different post functions can be configured in the workflow including webhooks. It is upto you how you want to configure it. Ravi
-
Hi @Paul Shrimpton Try moving your done or closed column to second last (not last) and take a look at your backlog again. Ravi
-
Hi @Judy Colonero This has been asked before. Take a look at this page here. You want to do something like this below. fixVersion in releaseDate("on endOfWeek(-2d)") I hope it helps. Ravi
-
Hi @Aileen Leitner Buck That is not possible with Jira native Dashboards. You would need an app for that. I personally prefer eazyBI. Take a look at this sample dashboard. I hope it helps. Ravi
-
Hi @[deleted] What exactly is not working? Do you see any errors? It can take a while initially but once the field mapping are done and the data type are matched the CSV imports works quite well. Take a look at the documentation. Ravi
-
Hi @Mike Hoyle There are some third party apps for Slack that can potentially do this - take a look at Jirio and Chatlio. Chatlio - will create embedded web form and link it to Slack. Jirio - will integration Jira with Slack. Take a look at them. Ravi
-
Hi @Silvia Technically it is possible to aggregate worklog from linked issues and display it at one place. It could be the actual estimate field or a new custom field. You would need additional app like ScriptRunner for Jira for doing that. Sub-tasks can be linked to any other issues in Jira. Ravi
-
Hi @Tauqir Rao Screen are associated with issue operations - create, view and edit along with worklfow transitions screens. For workflows you can have 2 transitions one for developer and other one for product owner (each with relevant screens). Then use workflow conditions to show only relevant transition. Ravi
-
There is a wonderful documentation here.
-
Hi @Mathilde BOISSEAUD My French is weak but yes it is possible to create a Kanban board from Jira Service Desk project tickets, if that's what you wanted to know. Ravi
-
Hi @Nancy Bonanno That is correct. The user needs to be either Jira Administrator or Project Administrator of all the issues associated in that bulk change. Take a look at this documentation. I hope it is helpful. Ravi
-
Hi @Emil BRaunstein If you don't want to manually export and import the issues then take a look at Exalate Jira Issue Sync app. There is an additional cost involved because it is not a free solution but it can potentially solve your problem of syncing selective issues/projects between two instances. Ravi
-
Hi @oliverwi Are you talking about creating Jira issues from Confluence? May be the applications link between Jira and Confluence is broken. Ravi
-
Hi @Steve Ong In case you want to apply permissions per issue then you need to use Issue Level Security. Here is the documentation. Ravi
-
Oh, you don't need to add the code in the Condition and Configuration.
-
Ok, you can try to setup logging to know more about why it is not working. You will get details where exactly it is failing.
-
Hi @Tzim Yes you can use curl, take a look at this page. You can do few things with user as well. This page has the complete list of REST API reference. Ravi
-
Hi @Arthur SALMON You can fetch last comment using something like this. CommentManager commentMgr = ComponentAccessor.getCommentManager() ApplicationUser currentUser = ComponentAccessor.getJiraAuthenticationContext().loggedInUser def lastComment = commentMgr.getComments(issue)?commentMgr.getComments(issue).last().body: ""…
-
Hi @Coco _El mejor_ Go to your project settings and then customer notifications. There is usually a template called Public comment added. In that template there is a variable ${comment}, when you include this in your template the comment added by an agent should be sent to the customer in the email. Read the documentation…
-
Hi @YTZ Here are some resources for you. * Jira REST API and examples. * Jira Server REST API Reference. * To practice with Jira easily and quickly use the Atlassian REST API Browser. This will let you play with the api and try out simple things. I quite often use curl or browser to play with the REST API and doing quick…
-
Hi @Mahendra Guru Yes you can use simple JQL like this. assignee = agent1 or assignee in (agent1, agent2) To get familiar with search functionality you can go to the Issue Navigator and use basic search. Ravi
-
Hi @Vineela Durbha This link has the code to fetch nfeed value. Give it a try. Ravi
-
Hi @John Adams I would check for the validator in your workflow transition first. Ravi
-
Hi @Fahad Siddiqui The Jira Administration | User Management | Users shows login details but not other details. You can look into database if you have access or use add-on like ScriptRunner. You can find some pointers here and here. Ravi
-
No problem. Have a nice day.
-
Hi @Renni Verho There is a suggestion for this requirement. Take a look at this and vote: https://jira.atlassian.com/browse/JRASERVER-32563 Yes it is a bit annoying and you will have to ask the users to use [~mention]. Probably add a description in the field to make user aware about this. I hope it was helpful. Thanks, Ravi