John Funk Community Champion

Hmm, that should work. But maybe try to add another permission for Create Issues for a Project role like Team. And then make sure the Team role has the users you want by name or maybe try jira-users as the group. Or just update the permissions above to use the group jira-users instead of Any logged in user. 

Ah, I understand better now. But, unfortunately, that is beyond my expertise. You probably need to do a new post with the information from your last comment. 

Hi Yvonne, Agree with Ismael for number 1 above - it should definitely work. For number 2, we actually have different statuses (and therefore transitions) for different types of resolutions. We use Discard for issues that are dropped and never started. We use Aborted for issues that were started but we are not going to…

So, you are saying that if you click the Plus sign on the left nav bar and choose your project, then you see Epic as an Issue Type in the list? But if you click on Create Issue inside the Backlog screen you don't see Epic in the list for the same project? If so, that is very strange as it works on my project. If that is is…

Yes, that would be really cool. You might open a support ticket with Atlassian to get that on their radar/roadmap. 

Hi Mark, Not sure that can be done. But what about going ahead and creating filters with the textsearch options already populated - especially if they are the same value for each field. Then the user just selects which filter to run. They should add the Project on the end if that makes it more flexible. 

So you can edit other fields but not Flagged? Does it even show up for you when you edit a screen? Also, while you are on the board, see if you can right click on a card and see if Add Flag is an option. 

You might want to open a support ticket with Atlassian then if the permission scheme is not working as expected. Sorry. 

Hi @Mark Oren - Did you get the answer you were looking for here? 

I hope they get that resolved for you. :-)

Hi Daniel - was this a help to you?

If that worked for you, can you click on the Accept Answer button so others can see the solution? :-)

Hi Nicole, You might try adding a Validator on the transition to Done that requires the Time Spent field to not be empty. 

Hi Peter, If you just want a quick way to view Done issues, you can create a Board with a filter that shows only done issues. Something like project = ABC and status = Done. You could show as many or as few columns as you want on the board - even just one column - Done. Be sure the sub-filter for the board does not keep…

Hi Teruhisa, You might try this article for help. https://bobswift.atlassian.net/wiki/spaces/JCLI/pages/17563670/How+to+import+JIRA+issues+using+CSV+or+SQL

Hi Benjamin - Welcome to the Community! If you are looking for the ID of the transition itself (and not really an issue id/key) then you can find that by editing the workflow, then click on Text to see the full listing of all transitions and find the appropriate ID for it. 

Hi Zhang - Welcome to the Community! You should check your Permission Scheme to only allow certain users to Browse the Project. 

I would start with your team leader. 

Hi Dinu - Welcome to the Community! I don't believe that is possible. I tried playing around with different Validators, but not all of them have the ability to do messaging. There might be an add-on app that would help with that. Typically, if you do not have permissions to create an issue on a project, then the project…

Hi Mitali - Welcome to the Community! If they key exists, you should be able to do that. But if they key does not already exist, you will not be able to do that through an upload.

Can you show a screenshot of your permissions for Create an Issue? 

Hey Elinor, It looks like you still need to create your own workflow with the statuses you desire (what you have listed in your last post). Then you can control who can do what based on conditions on the transitions. 

Hi Shruti - Welcome to the Community! A label is just a field on a form/screen in JIRA. Is that what you are tying to do? The label field is really just an open text field, so it is not associated with group. If that is what you want to do, then you need to create a custom field with a User Picker field type. I hope that…

Hi Joy - Welcome to the Community! Did you make sure that the users are granted roles on the project? The permission schemes are attached to Project Roles (or Groups, but you should use Roles :-). Just make sure the users are attached to one of the roles. 

Hi Sherlock, Are you using Cloud? If so, the + sign should work no matter where you are - in Backlog or not. Be sure you have chosen the right project and that Epic is an Issue Type for that Project (that it is in the Issue Type Scheme being used by that project). 

Hi Sara - Welcome to the Community! Maybe try adding an Activity Stream gadget to a Dashboard. See the screenshot below. It would give you only selected times, but hopefully you can quickly scan it to see the time or even do a CTRL F to look for times maybe. Hope this helps a little!

Here is what we use. It is a little more involved than most. We also use a flexible process where the issue does not have to go through Code Review, Merge, or Package Review. Package Review is used for iOS and Android app changes. Let me know if you have any other questions. 

Thanks Lukasz!

Hi Elinor - Welcome to the Community! I would suggest you still follow a Kanban process to handle your bugs. Not all bugs get worked immediately and should be a part of your backlog until ready to be worked. Plus, by having it as a part of a Kanban process you get full visibility into all of the things your team is working…

Okay - let me know if you run into any further problems. Can you click on Accept Answer on this ticket for me? :-)