Comments
-
Thanks for the feedback @Guido Menardi Could you please try the following constellation for issue filter scope: Location=${customfield_1} There should be no need for outbound Reference config with this.
-
Hi @Sandra Lawrence thanks for your question. Sadly, this is not possible. The simple reason for this is, that IQL will return whole objects and not only attributes. It is probably the same as JQL returns issues instead of custom field values from various issues. So the only thing you could do: aggregate asset attributes…
-
Hi @Amit Kumar Singh thanks for your question. I think the best way would be to get the data directly from the database. But I'm not a 100 percent sure would exactly you need, as you are asking for custom fields, issue types and projects in combination. Do you just need a simple list of issue types with id and name? Maybe…
-
Hi @Bryton Salisbury welcome to the community and thanks for your question. You were almost their with your past tries, but the input value is a little more complicated. It is a regular custom field like "customfield_10202", but the value is a combination of the project key and the request type name, like so:…
-
Hi @Trevor de Souza thanks for your question. Your starting point looks correct. Might be just a small piece missing. 🙂 Could you please post a screenshot of your rule config? You probably would want to branch on {{lookupObjects}} and for each entry use the create issue action.
-
Hi @Flavien Gache thanks for your question. If you are deactivating the option with the red x, the customers need to create an account before they can create requests. With your current setup, they only need to type in their email upon creation and an account is created in the background (which needs to be done, to set…
-
Hi @Arlene OConnor thanks for your question. You are totally right with your observations. To switch the reporter, which is the main recipient of the customer notifications, it is needed to add them as a customer to the project and request. Another option would be to add them as request participants, but that would also…
-
Hi Guido, thanks for your question. Just to be sure: Does the Location attribute store a link to another object or is it just a text attribute with the location name? From what I can see now, everything else looks good.
-
Hi @Mohammed Haneefa Farook thanks for your question. The display information is actually determined from the user information of the reporter. To me it looks like the reporting emailaddress has no display name added, as this person has never signed in (which makes sense, as it is a noreply address) I guess there is…
-
You are welcome. I'm glad I helped!
-
Hi @Noemi Pallotti thanks for the explanation. Having D as a seperate customer project, which is open for anyone makes it quite complicated. In my opinion, there is no solution to your problem using only one Jira site. Only thing I could imagine would be to import all of the 100k users into project D, but I guess they…
-
@Duc Anh Le as promised I tried several things and came up with a solution supported by the app JMWE. My workflow uses sample statuses, please don't mind the wording. Key is that there is a status in between the two approvals. This one will always be auto transitioned over, but we need to have a step for handling of the…
-
Hi @Noemi Pallotti welcome to the community and thank you for your question. Currently it is not possible to limit a domain to a single project in Jira. But I guess I'm not a 100% sure, what the problem is. You got lets say three projects with limited customer access and one project which is open for anyone. Thats actually…
-
Hi @Duc Anh Le I'm going to try this in my demo environment and get back to you within this week. There might be some other things we could test out. 🙂
-
Hi @Duc Anh Le , thanks for clarification. This is a really good approval workflow use case. I haven't had such a constellation before, but I guess it should be solvable. My idea would be to only use one approval status, but to modify the people need to approve via automation rule. * Ticket gets created and fields are set…
-
Hi @Kim Euker , thanks for your question. Could you give us a little bit more information about the field/input you are trying to use to limit the results? Are you trying to limit the results in the asset custom field context?
-
Interesting read. I will probably try that one soon.
-
Thanks for sharing Andy!
-
Thanks for the great thread. So many beautiful ideas. I'm currently planning to go skydiving in the next few months. Has been on my list for a few years now.
-
Van Gogh Alive an interactive Van Gogh exhibition
-
I really love Club Mate. It is probably more a German thing I guess?
-
Even though it is more a tree than a flower, I love the smell of lilac and the beautiful range of colors it can have.
-
We recently changed all water bottles and lunch boxes to stainless steel ones instead of plastic. Really like them :)
-
Still one of my favourites
-
Haven't heard about Lei day before, nice to know :)
-
New Zealand is still at the top of my list. And probably a longer camper tour through scandinavia :)
-
Hi @Duc Anh Le , welcome to the community and thank you for your question. As of what I can see, you are on the right track, chaining two Approval steps after another. Could you explain a little bit more, what your problem is? Maybe you could post some screenshots? If it is the decision for the 2nd Approval, you might need…
-
Hi @Tomáš Vrabec , thanks for your question. I totally understand the struggle your customers are in. From my perspective there won't be any lower DC tiers, as this is a product for bigger customers with certain regulations. What is the industry your customers are coming from? Maybe there are other customer examples that…
-
Perfect. Glad I could help :)
-
Hi @Pedro Silva , thanks for your question! You should be able to set the sender name to the name of the portal, via project settings > customer notifications > sender name. Detailed instructions can be found here Hopefully this helps, as my Portuguese is quite poor and I wasn't sure what should be changed in the…