Jack Brickey Expert

This is what I found however it doesn’t seem to cover the latest changes - https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/ still you should be able to navigate through creating a project using this documentation and just viewing the screens and making choices. 

Well there’s been some major rework in creating projects. The whole template infrastructure Is new to me to be honest. I will try to find some documentation that references in the new methods. 

I suspect the answer to your question is yes. What that text seems to represent is the health tips that the admin sent the project up chose when creating a request type. If you are a project admin go to project settings request types and find that request type that you’re referring to. Edit it and see if you can find the…

Hi Mark, I don’t understand the submit button concept you are referring to. I’ve never seen this but you mentioned that you have seen it before. it would be great if you could reference some documentation that I can review and comment.

That view is not configurable. However you can click on the button go to advance search and can change what is displayed. 

Only agents can make public comments. Collaborators can only make internal comments

Are the ones in the fixed status created in 2021 or prior? Above JQL returns everything in 2021 regardless of status. So if the fixed issues were created in 2021 and that would be consistent with the JQL. However if they were created prior to 2021 and that tells me that your fixed status does not equate to a done status…

Yeah you can’t use group. He would have to use “was in (A,B,C)” listing the users. 

There is no way to determine if someone has viewed an issue. They would need to take some action on the issue. 

Interesting idea. Certainly you could incorporate some external form app. But it does get kind of messy in my opinion

So maybe instead of saying current user you could use - assignee was in (A,B,C) now the tricky part would be if you didn’t get it assigned to anyone. So thinking about this more, to be able to do this I think you’re going to have to use some custom field that could be used to signify the queue. There may be another way I…

Yeah with the business projects those are default boards and are not configurable at all. Now you can create your own kanban board and what you need to do is set the location to be your profile you can’t send it to the actual project. Once you do that you’ll have a fully configurable Kanban board and you can achieve your…

Is this may be a business project? I’m wondering if this is a default Kanban board and not a fully featured board. 

I’m not exactly familiar with that new board of Jira work management. Is this a company managed project or team managed? Can you access board settings via the… In the upper right? If so then you need to modify your Jake you outboard filter to limit to the most recent three weeks

There are a number of posts on this already in the community. Here is one that might help answer your question - https://community.atlassian.com/t5/Jira-Software-questions/How-to-turn-off-new-view/qaq-p/1678683 

That feature is available in Jira service management but not a Jira software or Jira core. You might have a look at the marketplace one available addon app. 

Yes it is certainly possible and Company manage projects. Have a look at this article - https://support.atlassian.com/jira-software-cloud/docs/what-are-jira-workflows/ 

What is likely happening here is that you have the default roles set up search of new users are being added to that role. And then that role is being used in all the project’s permissions. What you need to do is ensure that the projects where you don’t want users to have access to you need to update the permissions so that…

I would consider using automation. Upon ticket creation if the issue type is bug then you can assign it to the proper person. 

If you have data in the spreadsheet you can convert it to a CSV file and use the import feature to import the issues into an existing project or create a new project even. See if this article helps - https://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/ 

Well I need to know a little bit more about your queues but let’s assume that issues in your queue equate to issues that have you as the assignee then you could consider adding the following to you date query and assignee was currentuser 

Unfortunately there’s not a single configuration to take the project off-line. But you could consider to either remove all the customers but that could be onerous, or you could hide all of the request types by not including in any group. This would result in the customer not being able to open an issue me a portal. Of…

Maybe this then project = IT and (createddate >= startofyear() OR statuscategory != done) that JQL should give you all issues for project IT created this year regardless of the status and any issues created before 2021 that are not yet resolved. 

Do you mean by the ones that are open prior to 2021? Do you mean to say any issue that was created prior to 2021 that are still in an open state? Sorry I’m just not quite following what you’re looking for here

Sorry left off some parentheses. project = IT and (createddate >= startofyear() OR resolutiondate >= startofyear())

Try this... project = IT and createddate >= startofyear() OR resolutiondate >= startofyear()

Issues cannot be assigned to teams they are assigned to users. Epics are no different than other issue types in this regard. Regarding plans the link that you provided was actually for server and in cloud advance road maps is part of premium not standard or free. 

No this cannot be determined 

This wording is not Configurable

I agree with Dirk on this. Allow the customer to say how important the issue is to them and the urgency. But priorities are generally set internally by the agent team.