Comments
-
You asked how do I reset their password. There is a Change password and that is how you do it. You share that temp pwd with them and then when they log in they can change it.
-
OOTB Jira doesn’t support ‘count down timers. JSM provides a version of that in SLAs but that doesn’t apply here. There are addon options that provide solutions that you could consider. I would check the Marketplace. Another option would be to use a custom field and Automation where a daily rule would run and check the due…
-
So if you want them to have access to Confluence and not just Knowledge Base, correct. If they currently appear in JSM list under User management then use the Migrate function to create an Atlassian account for them and then edit their details and click on Confluence access. Leave other product access (JSM, Jira, etc)…
-
To change their password click on the cog in the upper right, select User management and then select Jira service management. Find the user click on the… on the far right.
-
Looks like they decided on a bug - JSWCLOUD-21193
-
I had not seen this previously.. I like the confetti!
-
I tried this... Project = wgo and updateddate != 2020-08-26 and got back about 300+ issues. I didn’t inspect the results to verify none had updates on that date.
-
Actually that won’t work. As it doesn’t exclude 26th. are you sure the != date isn’t working?
-
Well I can’t say I have ever done that but try this... Project = ICS and updateddate < 2020-08-26 or updateddate >= 2020-08-27 you can adjust dates to meet your needs.
-
Yes assuming you have the customer notifications set up do send notifications.
-
Hi @Swarnima Kumari , can you clarify exactly what you are looking at? Maybe a screenshot.
-
OOTB there is not breach date. You can report on breached in a binary context (yes/no). You mention seeing previous KB. Can you share this detail?
-
i couldn't find much either. i did find this on Confluence. I wonder if Jira is similar. view-your-notifications
-
Thanks to Bridget for adding the images!
-
correct I should have conveyed that right off the bat.
-
are you sure the issue exists. might have been deleted. can you create a JQL that would show the issue and verify that it exists?
-
and they cannot edit workflow? hmmm, i see you are on server but would have thought it would work as it does in cloud.
-
I think I would do the following... Trigger: Issue created Condition: JQL - type not in (epic, sub-task) & "epic link" is not empty Then: Send email adjust condition to meet your config
-
you can give the project admin rights for that project only.
-
generally this has to do w/ permissions. For example you can only mention users that have browse access to the project. But it sounds like you are saying that you don't see any users and I would assume you must have some user in the project with Browse capabilities? In any, can you assign an issue to any user? if so please…
-
I haven't seen an issue but that doesn't mean there isn't. ;-) What exactly are you seeing? Can you go to admin > system > shared dashboard and see if you can find it, check owner and maybe reassign?
-
Original estimate (OE) is what you initially scope the work to be. Time remaining = OE - total logged work (unless you manually set the RE at some point when logging work).
-
Contact Atlassian Support and have them inspect your system.
-
of course....audit logging, if not done properly (configurable) can have undesirable implications on performance.
-
I would vote for an audit log solution over using email for logging. I wish that Cloud offered user admin access to better system logging. The current audit log under admin > system is inadequate.
-
the solution (and i think there is one) really depends on your ability to clearly construct your UC/scenario. Basically, can you construct a simply if-this-then-this-else-if this-then-this-else.... structure. I am thinking you just need tighter conditions to test what if/else block you need to execute. With that said, one…
-
according to their article on supported browsers, yes. I don't use Edge so can share my thoughts - supported-browsers
-
you could consider the following automation solution.... * add a custom yes/no field say maybe "self tasks" * create an automation to set/clear the new field --> trigger - field changed: assignee, condition: if/else compare assignee to reporter, set field to yes, otherwise if currently = yes then set to No.
-
I'm not sure I understand. It sounds like you want to setup an external email account and include that account on all notifications from Jira? Is this the case? If so this isn't really a Jira task as much as an IT task. They would set up an email for you (exchange, gmail, etc.) and then you as a Jira admin would have to…
-
Go to the project settings > notifications and inspect the various notification events. Ensure you exist in one or more of the groups or roles associated with the desired events. If you cannot access the settings contact you admin.