Jack Brickey Expert

This is associated with Confluence not JSD. In Confluence, If you are an admin you should see this here - cog > security configuration. At the bottom of the page you will see the XRSF section.

So your query isn’t going to work as stated. If you have a user that isn’t assigned to any story then they would be excluded but the filter. you should simply use this filter - type = story However, now that I think about it, I’m unsure if the two dimensional will display users with zero issues assigned or not. Bit a quick…

I experienced this yesterday and noted another post of the same today. I can’t reproduce so maybe it was fixed in my instance. You might want to report to Atlassian Support or just monitor for a couple days.

First that strikes me as an odd goal as it would go against good agile practices. However my opinion aside, you could consider using using Automation. It would necessitate some unique field value or other condition to succeed. Maybe a label could be added for every issue created in Slack such that the automation could…

Yes there is an active incident - https://jira-service-desk.status.atlassian.com/ 

Now I'm not sure I understand your question. Can you share your JQL? Which of the following (if any) are you asking... * I want to find all users that do not have an issue assigned to them for a given project * I want to find all users that are not part of a specific project * I want to find all users that are not part of…

Excellent. please update us here. As you are on the cutting-edge of archiving I'm sure others will be interested in your findings. :-)

none in OOTB Jira. You could consider setting up a PowerBI solution but that would not be in the Portal. You could also consider a different portal solution using the APIs and create your own. Regardless, you would need to consider addons or development. Here is one JAC ticket open that you may wish to vote/watch -…

Jira has the concept of Watchers. Watchers need to be licensed users in the Jira instance and have project access to the project in question. JSD has the concept of Watchers, as above, and also Request Participants. Request Participants are similar to Watchers but apply to Customers which are not licensed (free) users. So…

...well I can't comment on whether that is the case or not. JK....LOL!

Are you saying you want to set to unassigned or you are trying to stop this from happening? Either way hopefully the following helps... Two possibilities for the cause: * there is a post function on the resolution transition(s) that is clearing the Assignee. I have seen people do this because they feel that no one should…

I see. I was unsure as the Product Plan tag on this post says Standard. In any event, I can't say for sure as I do not use Premium. I would reach out to Atlassian Support. Given how new archiving is, I would not be surprised that there may be some holes.

you don't have the ability to add something to a Version, other than the Name and Description of course. As you said you could create a unique issuetype (or just use Task) and create one per version and use a checklist addon. you might check the Marketplace. I'm not aware of any addons but they may exist.

see if this helps - https://www.atlassian.com/software/jira/pricing 

i noticed this as well just yesterday. However, i just retested and am actually seeing the popup. If you can reproduce at will I would suggest reaching out to Atlassian Support to have them take a look. Or just wait a couple days and see if it returns. ;-)

a bit confused. In JSD the Assignee is an Agent and as such they use the JSD application to view their assigned issues not the Portal. The Portal is used by Customers to see the issues they reported as well as those they are Request participants of. if you are an agent and click on the link in the email notification indeed…

got it. indeed custom fields do appear different that system fields. I would suggest providing feedback to Atlassian on this using the feedback link under your avatar.

I guess I would say that is simply the way it is designed. The Create screen is implemented to be more of a "form" to enter data and generally captures only the info that is important at the time of entry. Whereas the view is intended to capture the full lifecycle of the issue and assist the assignee and others to…

yep I don't have a free instance stood up to play with. I guess I need to create one. :-) That said I checked the pricing site that shows high-level comparison and it shows that customizable workflows are available in Free so that would suggest classic is (was?) available in Free.

Sebastian, can you educate me on how you archived the project? While I am aware that project archiving has been a recent addition for Cloud Premium I am not aware of being able to do this in Standard. But, as I don't use NG very much maybe there is something there I'm unaware of. Regardless, assuming there is some…

@Nic Brough -Adaptavist- , is that true. I didn't think so but certainly could be wrong. My thought here would be that Andrey is using a Next-gen project where workflows do not exist, in the classic sense) to change.

Hi Amit, welcome to the Community. It sounds like you are trying to assess workload for your team. There are various ways to achieve your goal but let me start with what I "think" would be best. Create a Dashboard for your team and use various gadgets to assess workload. I like the Two dimensional gadget where you can have…

From dashboard? Or do you mean Kanban/scrum board? If you do mean “Dashboard” there isn’t a way to do this. If from a Board then select and drag/drop on your done column. Personally I would do this via a bulk edit via filter query result. This allows me to set various fields and add a comment, e.g. duplicate issue.

Hi Thomas, welcome to the Community. Basically you just need to create an issue type and associate it to a workflow that meets your needs. If you are not familiar with how to create/edit workflows please see the following documentation. To create a new Issuetype go to project settings > issuetypes > action > edit > add…

Hi John, this is a lot of questions rolled into one and to properly answer would take quite a bit of effort and also some follow on Q&A effort too. With tape said I have perused each of your requirements and I don’t see any that could not be met. With that said the devil is in the detail as often the “how” influences the…

These are all basic features of Jeera service desk. To receive a request created notification ensure that you are in a user role or group for the create notification. Similarly do the same for various issue updates: comments, transitions, etc. notification configuration is accessible to admins under project settings >…

I cannot access that link nor should I be able to. Can you explain what product?

No. The email subject must have the issue key for JSD to consider it as a comment to an existing issue. If the user replies to the email from a JSD notification it will result in a comment

Time estimates is not limited to Story issue type. You can estimate time for pretty much any issue type. You can estimate in time or story points. You might find this article of use - configure-estimation-and-tracking 

Create groups and add members according to the specific restrictions. Edit the workflow, assuming you are using Classic project and not NG, and set a condition on each transition that restricts the ability to execute the transition based on being a member of the group.