Comments
-
is that pasted in text or typed? I was trying to reproduce but w/ the new editor I cannot easily replicate.
-
Consider using Automation. Trigger - issue created Condition - JQL - type = sub-task Condition - JQL - something unique to ensure the action is triggered only when desired Action - update the parent in some way, e.g. add comment - "sub-task xxx added"
-
Hi @Gan Zhi Long , the ability to change the field type is not supported. Depending on the details of your specific situation the best option to try is to create the new custom field and then run various JQL queries based upon the old field's values and bulk update the issues setting the new issue value. You might even be…
-
Hi Jace, what do your project Notifications look like? Are you sure that they reflect the desired update notifications for the roles/groups associated w/ your users?
-
@Steve Hamilton , any luck here?
-
did you give them the URL? If so they should get something like below.
-
a screenshot would be nice. one that displays the detail issue view for a resolved issue.
-
Sure. You have Automation built into Cloud. You can set up a scheduled rule to run weekly and create as needed. If you need assistance LMK or have a look here - automation-triggers
-
so for the first issue are you saying the Create appears to be successful (no error message)? Assuming so, do you not see the momentary pop-up in the top righthand corner when you create? Let's do a test... * Create an issue * Observe top right. Popup? Yes - click on the link in the popup and observe. No - proceed to 3. *…
-
Hi Martin, Start by looking at the 2-dimensional gadget on the dashboard. You can create a filter like below. project in (a, b, c...) and resolutiondate >= startOfMonth() Then in the 2-D gadget maybe choose Y-axis = Assignee and X-axis = Project. Now you may wish to reverse the x/y or you might want a different x-axis but…
-
Agents can always add tickets. They don’t need to be Customers too. In fact agents often create issues on behalf of their customers.
-
Agents are not or should not be customers. I too find configuration of customers and agents confusing in JSM. The purpose of the drop down under people is so that you can select multiple roles for certain user if desired. Generally users fall into either SDT or Customer role.
-
No do not do this. Agents should not be customers too. It creates issues with notifications.
-
I haven’t done this so the following conveys my suggestions. * make sure you have uninstalled the app * check if the app is shown in any of the permissions on your projects
-
Hi Roxanne, welcome to the Community. I’m going to assume that you would actually use JSM and not JSW for this since you are working with external customers. Reading thru your post one thing strikes me as making this challenging - associating symptoms to workflows. Now maybe this isn’t really a requirement. It isn’t that…
-
I would suggest trying a different browser to check the permissions. Unsure why you would not be able to access the permissions page if indeed you have admin permissions.
-
thanks for the confirmation. I have not idea if it is either but my guess would be no. I would suggest reaching out to Atlassian support if you don't get an good answer here.
-
I have not played w/ organization in Automation. I found this thread that would indicate it is possible - Smart-value-for-Organization . See if it gives you some clues. Note the ticket you posted wasn't calling out a syntax that works but a suggestion of what it might look like.
-
For Sheets, I have not done this so can't say for sure. Your original post wasn't calling out Jira Cloud for sheets so I was answering accordingly. I poked around in the Community and found a few posts that might help. From what I read Sheets does allow for automatic refreshing but no clue how it works or if you can…
-
personally I would do this outside of Jira. I can imagine planning an entire year out would inevitably result in constant change. as each sprint approaches you can then use the external reference to build the upcoming sprint. Alternatively, maybe your create a dummy scrum board for planning then clean things up as you move…
-
is there anything in the email logs? project settings > email requests > view logs
-
i was going to suggest the second option as well but a bit different. Use automation to send the notification out. But rather than a notification date just add a comment if notification is triggered, e.g. "notification sent". Then when you JQL runs on say day 6 the issues updated the day before will not be triggered. by…
-
Customers will not have access to the applications and therefore cannot see things like reports. If you want to give a customer access then you would need to migrate them to a licensed user but be cautious here since, beyond the cost, do you really want them to be a user in your instance? If you do then go for it. What you…
-
you don't manage subscriptions in the Jira Cloud for Excel. you create a subscription w/in Jira itself. * Advanced search for issues * enter JQL and get desired results, columns, etc * save filter and give it a name * click on the details link at the top of the filter * click on manage subscriptions * configure desired…
-
IMO... * definitely create a unique project to keep internal separate from external. there are lots of reasons for this but they depend on your exact scenario. still i'm confident in my statement here regardless. * organizations are only required if you ultimately will have multiple clients (groups of customers).…
-
you might find this article to be a good read - Restrict-the-creation-of-tickets-of-your-Jira-Service-desk-Cloud
-
note domains don't come into play here except where it just so happens that you have a 1:1 relationship between project:client-domain.
-
This is precisely how JSM works. In JSM email handlers (channels) are per project. Each project has its own email that can be used to open issue specific to that project. When an email is sent to a project email then issues will be added (or comment added) to the specific project. project1@mycompany.com…
-
Anyone that needs access to Jira must be licensed. You can control what projects they have access to via the project settings of the project.
-
yes it works for cloud that is why I suggested it above. Have you attempted to set this up and having issues?