Kai Becker Community Champion

@Marta Woźniak-Semeniuk @marI agree on your opinion regarding the estimation of issues. Never the less, software is usually developed for customers that actually pay for it. So there is definitely a need for time tracking and further billing. But thats just my personal opinion.

Thanks for the reminder @Dave Mathijs 

Haven't done this yet, but this seems very interesting.

We usually plan some project closing stuff. A little team event with socialising, but also a retrospective for further improvements.

Totally agree. Kick-off meeting is definitely essential for a successful project.

It should be visible right under details in the rule config dialog.

Hi Danielle, could you give us some more information? Where is the teams value stored? Do you want a list of issues? Do you want to get the report via email? Or on a dashboard?

Hi Pas, no problem. I updated your code. Line 22 is the log I meant and line 33 shows the update with the option itself, instead of the option value. That should do the trick: import com.atlassian.jira.component.ComponentAccessor import org.apache.log4j.Level import com.atlassian.jira.issue.ModifiedValue import…

Hi Nate, a sorry, I misunderstood that part. Thought you wanted to have just an url per field. But you could still create a paragraph field? That should have the wiki style renderer:

Ok, I get it. So I guess the easiest way would be, to handle this via workflow buttons. And then you have to add a addition/subtraction to the corresponding post function. The only downside to this solution is, that you will get a reload with every single transition. Another solution could be a single select list. But this…

I don't think that something like this is possible. Maybe you could give us some more information about your use case, to find another suitable solution?

Could you please share an example of your csv file? First row (anonymized) should be sufficient. Usually it is just a format problem. The csv file definitely needs a header row, so this might be the first thing to check

Hi @Nate Dickinson why not use a URL custom field?

Hi @Dwight Holman actually this is a common use case in our customer environments. We usually use a setup like this: * JSW dev ticket is created from first JSM request * further JSM requests are linked to the dev ticket * JSM request will stay in "pending" status * when the dev ticket is resolved and feature got deployed…

Dr. House <3 

Yes! No doubt on this one :D

Sorry, but this is wrong. This field is the issue reporter, not the assignee. It automatically defaults to the currentUser for none agent users.

Hi Baskar, could you explain what the purpose of this setup is? Why would you create a board filter for project board A, which only allows issues from project B? This does not make any sense to me. As the filter is limited to project B, I guess create screen defaults to this project. Usually the create screen recognises…

Hi @Google Bard , what do you mean by "service requests, events and email requests start with 1" ? Do you mean the ticket key? Like IT-1 or something? Easy answer: Create 59401 issues via REST API and delete them afterwards. There is no other way to increase this sequence.

There is only one automatic way to achieve this: Modify the notification template and add the signature to the template (you can use some variables there) <sitename>.atlassian.net/jira/servicedesk/projects/<project_key>/settings/customer-notifications/template

Hi @Johanna Vehkanen the problem here is, that A2 will get a notification from Jira, because of the comment from A1. So it is not an explicit notification from A1. I guess this would be difficult to tackle, as you want A2 to get some notifications, but not all. What you could do: In customer notifications, set recipient to…

Perfect. Glad I could help :)

Hi @Cory Cigas would you mind sharing your code, to better understand the setup? To be honest, I guess you will be more successful asking this question on stack overflow, as it is not quite a JSM problem, but I will try to help anyway.

We usually use automation rules in our customer setups, to set a corresponding request type for moved issues. Depending on the source project, there could be some differentiation, but most of the time we stick to a default request type, that is also used for email requests.

Hi Inetinfo, I would suggest creating a new single line text field "Resolved by" and populate it via automation rule: In my example, Arbeitspaket would be your "Resolved by" field, as I didn't want to create a new field, just for testing. The rule trigger is configured like this:

considering your current setup, there is nothing out of the box, that will give you this information. There are several ways though to solve your problem. The easiest would be a 3rd party app you have to install. There are several ones on the marketplace, this one for example is…

Hi @mahmoud burhamy do you use Jira Cloud or a self hosted Server/DC environment?

Hi @Magdalena Zhisheva you are totally right. I meant JSM Cloud :)

Hi Inetinfo, could you please give us some more information? Are you using Jira Server/DC or Cloud? What do you mean by "This information must also be shared with DANA" ?