John Funk Community Champion

Very ingenious! :-)

Hi Curt, Try this: Hey team - we've got the following issues left in this sprint:{{#lookupIssues}}* {{key}} {{summary}}{{/}}

こんにちはYugo-アトラシアンコミュニティへようこそ！ 1つの方法は、ユーザーごとのアクティビティストリームを表示するダッシュボードを作成することです。 ダッシュボードには、ユーザーごとに異なるアクティビティストリームガジェットが必要になります。これにより、ユーザーが行ったすべての内容と時期が表示されます。アクティビティをすばやくスクロールして、そのユーザーがツールをどの程度操作しているかを把握できます。 Hi Yugo - Welcome to the Atlassian Community! One way might be to create a Dashboard that shows the activity stream by…

Hi Jane - Welcome to the Atlassian Community! There's not exactly the functionality in Jira that you describe but close. You can create a base project, or template project if you will, and then base future projects that you create on that project. When you create a new project, you have the opportunity to create it based…

Ah! I forgot about the Lite version! It's been a long time since I used that one. :-)

What Issue Types are available in your Issue Type Scheme for that Project? And do they following different workflows?

Great! Glad to help as are lots of other folks on here. Don't hesitate to ask questions. :-) And if this took care of the question for you, do you mind clicking on the Accept Answer button above so we can close this one out? Thanks!

Hi G - I believe it is 20. There is a feature request to increase that which you can vote for and follow along with here: https://jira.atlassian.com/browse/JRACLOUD-69218

Have you tried to log in as him to see if you see the problem? Also, maybe go to a Permission Scheme on a project he should have access to and run the Permission Helper. 

Yes, sorry - meant to tell you to do the Hide on that field since it is a System field. Glad it is working for you. :-) Can you click on the Accept Answer button above to close this one out? Thanks!

Do you have all of the issue types in your Issue Type Scheme? Do the two different Issue Types map to different Workflows? If yes to both of those, the when the user is in the card/issue, click on the 3 dots menu and select Move. From there, they should be able to map it to a new Issue Type.

Hi Alison - Make sure he has access to the products in the User Management section of Jira. Also make sure that he is in the appropriate groups. 

Check the Field Configurations file for that project. It probably has the Resolution field as required. Change it to optional and you should be good. 

Hi Ted - yes, this is certainly doable. First, though, the new Issue Type must be in the current Issue Type Scheme used by the project. If it isn't', you can simply add it. If the new Issue type is associated with at different workflow, then the user will need to do a Move on the ticket to move it to the Issue Type - it…

Great! Glad to hear it is working for you now. 

@Erik Britt-Webb - If you are a Jira Administrator and Seema is not (is just a Project Administrator), then I suspect the workflow is share and not unique to that project. If that is the case, Seema will not be able to edit the workflow. 

It’s really more of an education issue at that point more than anything else. 🙂

No, they would need to either move it on a board or change it in the Queue before they respond. They shouldn't open the card first and then change the status. 

Hi Shira, We have actually added a custom number field that we then use to indicate additional priority level within the same Jira priority. 

Hi Jean-Yves - Welcome to the Atlassian Community! One way might be to implement Issue Level Security. If the issues are not assigned to them (that is they are not the assignee) then they can't see the issue. So if it is not assigned in the backlog, then they cannot see it. But you can make it so that other users can…

If you are using a JSM project, you should be able to change the status in the Queue. That should be immediate. Also, if you are using a board, then dragging the card to another column should immediately let other users know that the board has changed and they need to refresh first. Is this a JSM project? Or a Classic…

Hola Cristian - Bienvenido a la comunidad de Atlassian. Implementaría seguridad de nivel de problema. Con eso, puede crear un nivel de seguridad que le permita al usuario actual ver solo los problemas que se le asignaron. https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/

Hi David - Welcome to the Atlassian Community! I know the Atlassian team is working to provide that functionality for the board, but not sure when it might get added. In the mean time, I would do what you suggest and add another status to the workflow without it being a Done status category. 

Hi Lindsey - Welcome to the Atlassian Community! I would implement another step in your workflow where the technician pulls the card to the next column or changes the status to Responding or Underway or In Progress or something like that, before they actually start responding. That way, if another technician goes to change…

No, there are no known free alternatives. :-(

Hi Navaneeth, No, this is not possible without add-ons in Jira Cloud. And about the only one I have worked with that can do that is ProForma Forms. https://marketplace.atlassian.com/apps/1215833/proforma-forms-checklist-for-jira?tab=reviews&hosting=datacenter

It says your Simplified Workflow Scheme is shared by 5 projects!!! It should not be! It should only be attached to the original project. Since it is shared you must be a Jira Administrator to edit the workflow and not just a Project Administrator. 

Then what error are you getting when you try to add a status to the workflow?

You have to be either a Jira Administrator or a Project Administrator to edit a simplified workflow. 

Please be sure you have published the workflow.