Kelly Arrey Expert

If this transition works for this user for some Epics but not others, then that makes me think it's not a permissions issue. Is there some other condition or validator on that transition, and the data in the ticket doesn't pass the condition? For example, the transition could be checking that a specific field is filled in…

Hi @Izla Kesler, You could try adding sub-filter. That's described under (Kanban only) Adding a sub-filter on the page @Fabio Racobaldo _Catworkx_ linked above. For example, something like: * status != Done HTH, Kel

Hi @Alvaro TL Can you share a screen shot of the Create Issues permission from the Permission Scheme? Thanks.

Another hack line of attack which you could try if you really want to hide it is to: * put the field on a separate screen * associate the screen with one or more workflow transitions * trigger the transition via the API

But you can write automation to copy a version from one project to another, after which I think you could get this to work. 

Hi @David Goldstein I don't think you can make an Epic a "parent" of a Story, say, from the Epic. The way I understand it, you have to view the Story, and then fill in the Epic Link field in the Story. Does that make sense? HTH, Kel

Hi @Omri Zeman Look for "Create a borderless background behind the value" on this page of the docs.

Hi @Amed Moreno, Atlassian Support has opened a bug with Development for the above. They're tracking it as JRACLOUD-81160. I'd encourage anyone interested to go and watch that ticket and add yourself to the Affected customers list. The Support Team looked into this and found that, for fixVersion, the automation was…

Hi @Sowmya Chandrasekhar , yes, you will have separate reports for each board/team.

You might want to try the validator first - you may decide that you don't need a message custom field after all.

Hi @Phil Bustin, Another approach would be to add a "Field Required" or "Field has been modified" validator to the transition, and include a message that would be displayed if the user doesn't enter/change the value.

@Mohammed Siyad If you use Jira Automation, you can trigger a rule using the Project Created trigger.

Hi @Pierre Leroux We needed to be able to assign work to teams long before Atlassian Teams were implemented, so we: * defined a custom single-select field we called Agile Team * defined Jira groups to associate members with each team This has turned out to be superior to the various Atlassian Team implementations for our…

@G subramanyam Your filter returns High Priority issues currently in Deployed Status which were created last year. Please see Bill's suggestion above which takes into account when the issues were transitioned to Deployed Status. 

Hi @Carolina Halbwachs If I were you, I'd try this before going to Jira Automation: * Write a filter something like: project = XYZ and assignee = currentUser() and "Project end date" > startOfDay() * Save it under the filter name "Please update the following issues" * Create a subscription to the filter* Subscribe all the…

Hi @Sowmya Chandrasekhar, if you're following scrum ceremonies separately for two teams, then each team should have it's own Scrum Board. Each Scrum Board should have a Board Filter which returns only the tickets assigned to that team. You could filter off a Team field value, or a component, or a label, or some custom…

Hi Joshua, sorry, not my app, I was thinking that if JXL implements a "global search and replace" function analogous to Excel, this would do what you need. It's not clear to me from the documentation that this exists. I'm hoping that someone like Hannes from the tool supplier could give you some specifics. HTH, Kel

Hi @Joshua Dumas, this sounds like it might be a use case that JXL for Jira or some similar app could help with. @Hannes Obweger - JXL for Jira, can you offer any suggestions? Thanks!

@Erikas Kersnauskas You want "Technical issues and bugs".

Glad this is working! As an aside, the Log action is very handy for debugging stuff like the above.

Hi @Amed Moreno, welcome! I tried it out and I think I'm running into the same problem as you - I can see the "toString", but not the "fromString". I've logged a question with Atlassian Support.

Hi Kieran, try giving "Browse projects" permission to your Viewer role.

Hi @Kieran Curtain, There are two main components to Jira permissions: * Project Roles - the People tab in your Project settings is where you assign people or groups to various roles in the project * Permission Schemes - the Permissions tab in your Project settings is where roles are associated with permissions - there are…

Hi Phil, So, to start with your last question: * A Screen Scheme associates screens and issue operations (create, view, edit). * An Issue Type Screen Scheme then associates Issue Types with Screen Schemes. Your first screen shot is the Issue Type Screen Scheme, and the components under each Screen Scheme are the Issue…

Here's some documentation on this topic. The move operation will prompt you for the status mapping, so you shouldn't need to a separate bulk change for each status. But if the workflows are identical, this should be trivial.

Here's my rule. I was able to get this working without your hack Walter.

Hi @Phil Bustin, If you want to move Sprint from the right nav bar to the "main" area: * Open the issue details view for a specific issue * Click on the Configure gear (bottom right) * Drag the Sprint field from Context fields to Description fields * Click Save changes If you want to see if Sprint is on the Edit screen: *…

Is it possible that Sprint is not on Phil's "Edit Screen" and that's why he can't edit it?

As an aside, I think that deleting Jira tickets is generally considered to be a bad practice. It will break links if any exist anywhere, and if someone tries to follow such a link, they'll get a message something like "You can't get to this ticket - maybe it doesn't exist or maybe you just don't have permission". This in…

Another point is that if the new issues are returned by the board filter, by default they go to the bottom of the backlog, so they might be "there" but not visible until you scroll way down.