Comments
-
Hi, @Robin Stemmers ! Also you can try a workaround, which I got from here. Look through the JMWE app.
-
Hi. @Victor Mutambuki ! About what global elements are talking about? Can you give more detail information?
-
Hi. @Chiragkumar Rupani ! Can you notify us within this question here after fixing (i`m watching it =))?
-
Hi, @amit sandilya ! Can you tell us the reasons to rollback? What`s go wrong? Why not to use 'old vision' in 3.xx?
-
Hi! Will the webinar be recorded? Is it possible to get it?
-
Of course, push the button "create issue", set JSD-project and correct issuetype, then you will see "issue-create-screen", where you can easily set the value to fields Sprint and Epic like i told before.
-
@Joe Pitt , thank you for your comment, really useful! How many users are on your instanse? How many jira-administrators do you have?
-
Also I can recommend you to read an article - Jira Service Desk: How Jira Service Desk works with Jira Core/Software, where you will find usefull links.
-
Hi, @Calderara Serge ! @Alexey Matveev really have already answered your question. 1. You can add 2 fields to JSD-issue screen and set the values : a. Sprint b. Epic Link 2. Change your Scrum-Board`s Filter Query (add there JSD-project, for example) 3. Add JSD-status to correct column of Scrum-Board(Configure - Columns).…
-
The main idea of @Max - we have 2 different instance of Jira (JSD(1 and 2nd line of support) and JSW(3-rd line)). Now we are trying to make integration through webhooks, for example, we will create a transition 'send to 3-rd line' with webhook, which will create a ticket on JSW (another instance) andfurther information…
-
Nice out-of-box decision!
-
Hi, @ebusinesspl ! It is possible to configure a project's email address, which is the email address that notifications are sent from – i.e. the 'sender address'. Look through this article.
-
Thank you, @Earl McCutcheon ! Nice news!
-
Hello, @ffngneiger ! Interesting question! What business case do you have?
-
hm, maybe you are right, I thought that it was another problem - just setting value in exact issue.
-
Hi , @Sayali Puranik ! Yes, it is known problem: * JRASERVER-12400 * JRACLOUD-12400 But you can mouse over the word "edited" and see who and when was the last editor. It is better than nothing:)
-
Hi, @sunil tattimani ! You can create new transition and set there screen with this field and a condition on transition to show it just for exact group(Engineering team).
-
Hi, like I know, it is impossible in the improved interface: * Commit issue assignee: In the improved planning interface, you now assign issues to assignees, and not team members anymore. With this behavior by default, you no longer need to configure this option for your plan. Other changes you can check here.
-
I have tryed similar case on server, i think it should be the same on cloud.
-
Hi, I think, that the matter is that JSD-Customers don`t have permissions on "browse projects" and "assign issues" - and it is correct, because Customers don`t use licenses. Like an out-of-box solution, you can create, for example, select-list field and show it on Customer Portal, then using JSD-automation rule(for…
-
Добрый день. Инструкция по устранению , даже на русском языке:)
-
I agree with @JP _AC Bielefeld Leader_ - Comala is nice solution! Here you can see a detailed comparison of Comala`s apps. For Cloud you can try : * Comala Approvals for Confluence * Comala Workflows Lite
-
@Arabinda Mishra , does it help for you? If you have questions - feel free to contact me.
-
Hi, @Jessica Anderson ! If i correctly understand your case, you can create new custom field (date picker), where you will set a date of getting info from the Client- look throught this article. standart field "due date" - will be your project`s due date. Also you can create a new filter and subsribe on it to control new…
-
Also we used for similar cases - Elements Connect (formerly nFeed) But there is no Cloud versions.
-
I can recommend you ScriptRunner for Jira. Case with anonymous portal - using different automations(post-functions/listeners) to identify users. Case with finding simillar issues - you can create Scriptrunner`s custom field, where you can add your JQL (set hard logic of identifying similar issues). In Scriptrunner`s…
-
Hi, @Jordan Lem ! ScriptRunner for Jira will be excellent solution to your case, It has post-function 'Clones an issue and links', also you can read this article.
-
hm, you can create simple process "get a call'. for example users can create a task : 1. from the Portal 2. send email to JSD-mail It will be separate queue, where "JSD admin" will get the task, then Close it after making call. You can disable notifications for Customers for this issue type.
-
Hi, @Luis Cabezas ! i think the easiest and the most comfortable way is creation new custom field with select-list, where you will check the certain Actives of company(for example, "Networking" etc). Then use this field to certain queues. Also you can show it on Portal for Customers then use different automation rules, etc.
-
Hi, @Arabinda Mishra ! JQL will be: 1. component is EMPTY 2. component in ( "A" , "B", "C") 3. component = "A" and component = "B" and cpmponent = "C"