Jack Brickey Expert

@Daniel Reis, it was definitely tedious but that was partly driven by trial and error. I have a document (confluence) that captured what I did. I'm happy to share with you but will need to export to word and clear out names, emails, etc. Too, I can't say that it is 100% accurate as I can't recall if I updated in the final…

cloud and memory only. It has been several months since I ran into this and that is what I recall. I did a quick search in documentation but didn't find anything which is unfortunate for sure. One would think that the expiration would be the same for both cloud an server but I can't say for sure. maybe someone has recent…

hi @Susan Hauth _Jira Queen_! The last time I checked it was 7 days which isn't very long. It may have changed as it has been awhile.

There are a number of other threads discussing this in the community. There is no way to prevent the system admin from having access. As with any application managed by IT in a business someone in IT is going to have access to sensitive info. One option is to use encrypted attachments with only privlaged users having the…

server or cloud? before I start let me say that I switched back to the old for various reasons I won't go into here. in Cloud click on the magnifying glass and you will see "Boards" section w/ a view all boards selection. click that and from there you can create a new board. that is one way.

In response to right-clicking comment. Yep that will delete the issue completely. That is my bullet 1. If that is your goal then you (or the admin) needs to provide you with permissions to delete issues for the project.

As @Nic Brough -Adaptavist- is alluding to, the devil is in the details. * If you truly want to delete an issue, removing if from the project never to be seen again then you need permissions to do so as you mentioned. * If you just don't want it on my backlog/board, they you could use something like a label "HideOnBoard"…

@Seth Silvernail, as @Jobin Kuruvilla [Adaptavist] indicated you cannot have both methods appear on a board.

I'm on cloud so can't speak to this definitively but see the following which would indicate upgrade to 7.4+ Backlog in kanban board

@Nuno Rocha,Adding to @Nic Brough -Adaptavist- response maybe if you conveyed what your end goal is there may be a different approach. 

@Lynn Shriver, in fact this is how the Jira products work. By editing the default Create Issue screen it will modify it for all issue types that use the default Creat Issue screen. If you wan to only change a specific issue type for a specific project then copy the default, rename and modify to your needs. Finally assign…

that is odd indeed!

thanks for the info. have never used the that template. keep us posted. In the end you may want to write up a clear summary as a solution so others can benefit. Too, if you are finding what you believe to be a bug then you should open a ticket w/ Atlassian.

@Walter Buggenhout, in fact I'm sure you are correct on the new UI being the cause/driver. I don' think it was nefarious but simply an unfortunate side effect. Regardless, I'm really not sure what Location actually is used for and don't care that I have to use my profile as the location. As long as I can have my boards. :-)

@Rich Ireland & @Walter Buggenhout, you are RIGHT! It appears that this is a recent change by Atlassian. I have been creating boards based upon business projects, JSD projects and software project for a long time. They have added a new parameter to board creation called "Location" and it is that field that must refer to a…

@Rich Ireland, not sure I understand what a business board is. You have the options to create a Scrum, Kanban or a recently added (cloud anyway) Agility board type. The next screen (below) gives you options for setting up the filter to be used for the board. Note I'm not using just Core so maybe there are differences that…

Are all issues duplicated in the S9 on both boards or only some? Do any issues in FRYP or Phoenix Platform happen to have label RPA-2017? Can you place "()" as below and observe? Board B: ... (issueFunction in subtasksOf("(project = RPA OR labels = RPA-2017) AND issuetype in (Story, Bug, Spike, Test, Epic)")) ...

can you provide the filters used for each board? that should help w/ resolution.

keep in mind that whatever you do you will have owners for filters used on the dashboard and the dashboard itself. Only the owner(s) can make changes. you don't need to be an admin to create/own a dashboard.

@Markhornman, you may look at this add-on. Not sure but might meet requirements. 

@Robert Six, please share an image of what appears here - Project>Project Settings>Customer Notifications

Please vote for and watch JSDSERVER-366 or the cloud counterpart as @Andy Heinzer mentioned. 

Understood and agree it would be useful to have within queues. In the meantime there are alternatives. 

agent permissions are per project. You can create queues per org and direct agents accordingly but that does prevent them from accessing other org queues/issues. 

Double shot of espresso followed by lots of Water with lemon. 

I assume you mean 'and not have to give 2nd/3rd level support users agent properties'. If you want user to be able to edit/transition they have to be agents.

@MoroSystems Support, the "is" operator is not supported for Approvals field. @Josip Šćirek, the only thing I can suggest right off is to use the "pending()". If I find a better solution I will add here.

not sure how/why the plugin is being used to send email notifications since that is native in JSD but I'm sure there is a reason. can you check the Customer Notifications and see what notifications are enabled?

yep. tickets/issues do not belong to a board. Boards are simply filtered views of your database.

Keep in mind that queues are simple filtered lists. You can use the other native filter methods, Jalisco save filters and Kanban boards. I would suggest looking at using Kanban boards for moving issue thru the workflow and for bulk assignments I would define component leads, and/or use bulk edit feature within list view.