John Funk Community Champion

Comments

  • You cannot have an issue that exists in two projects at the same time. You can create boards that show issues from two separate projects with a filter like: Project in (ABC, DEF) But an issue can only be physically attached to a single project. 
  • Hi Irena, What is not working? Is there an error? Can you share a screenshot of the Audit log?
  • Hi @Benjamin Rosenek - Welcome to the Atlassian Community! Try putting in a Branch rule / related issues component after the initial Sprint Created component. Use the value of Issues in the Sprint when you add the Branch rule component. Then give it a try.
  • Hi Jonathan - Welcome to the Atlassian Community! Cards in the Backlog have a Status of Backlog. So to see those issues in a filter it would look like: Project = ABC and Status = "Backlog"
  • Hi Todd - Welcome to the Atlassian Community! Can you share a screenshot of what you have so far? Basically, you want a rule for a Transition to a particular status to cause the value of the Assignee field to be updated with the value of the Sales field. Correct?
  • Hi Linda, Swimlanes on a board are unique to that board and do not affect any other boards. They are based on a filter/query for that Swimlane. 
  • Hi Michele - Welcome to the Atlassian Community! I am a little baffled by the question. What field are you trying to update with the "technical answer"?
  • Hi Alexandra - just to touch on a few things that Jack hasn't mentioned: The blue, gray and green colors represent Status Categories for statuses. Blue are In Progress statues, Gray are To Do statues and Green are Done statues. So you can actually use the StatusCategory in filters to see those status groups of issues. The…
  • Hi Silvia, I am not sure that I completely follow the situation, but hopefully this will help a little. Statuses on columns of boards (and available statuses on the right hand side in Boar Settings) are shown as a result of workflows attached to the project that the board uses in its filter. So if you are missing a status,…
  • If you have two projects - project A and project B and you want to move issues from A to B. 1. Create a filter for Project A, something like: Project = ABC 2. Do a bulk change by clicking on the 3 dot menu to the upper right. 3. Choose all of the issues and select Next 4. Choose Move 5. Follow the rest of the prompts. 
  • So you don't need to create new projects, you just want to duplicate or move the existing issues/sprints to other projects? I am a little confused at what you are trying to do exactly. 
  • Great - glad I could help!
  • If you have two projects - project A and project B and you want to move issues from A to B. 1. Create a filter for Project A, something like: Project = ABC 2. Do a bulk change by clicking on the 3 dot menu to the upper right. 3. Choose all of the issues and select Next 4. Choose Move 5. Follow the rest of the prompts. 
  • Parece que fueron creados a partir de dos herramientas diferentes. ¿Puedes crear exactamente lo que te gustaría ver usando texto simple de MS Word u otra herramienta de texto?
  • Hi Lucas - Welcome to the Atlassian Community! You can bulk Move the issues from one project to another. Just make sure they use the same workflows and issue types. 
  • Hi @SPARC - It depends on the type of project. You can't do it for Service Desk or Next-gen projects but you sort of can with Classic projects. You can create the "template" project and then when you create new projects, base them on the "template" project. 
  • Hola @LiquidezCorporativa , Debe hacer clic en la casilla de Jira Software para que el usuario tenga acceso.
  • Hi Rebecca, Make sure the Global Permissions to Share Filters is turned on. 1. Go to Settings > System 2. Go to Global Permissions 3. Find Share Filters and Dashboards 4. Check your permissions there. 
  • For cases like that, I actually create a separate board that only shows the Done column. Then you can order it any way you want there. :-) But we do weekly releases to clear the boards so they don't build up that long anyway. It also gives us a good idea of our Throughput for the week. 
  • Hi Babu - Welcome to the Atlassian Community! Take a look at this post and see if it helps guide you: https://community.atlassian.com/t5/Jira-Service-Desk-questions/External-User-Access-to-a-Single-Project/qaq-p/1328371
  • Hi Brittany - Welcome to the Atlassian Community! You can't really implement what you describe. The closest you could come is creating Swimlanes for every combination of user and labels that you have. And I don't think you want to do that. They would not be Swimlanes within Swimlanes, but just different Swimlanes in a…
  • Hey Scott, There is an open bug for this for the New Jira Issue View. You should vote for it and follow it here: https://jira.atlassian.com/browse/JRACLOUD-72024 But you could switch back to the Old Jira Issue View and you can change the sort order there. 
  • Agregue esto al final: Código Jira: {{baseUrl}}/browse/{{issue.key}}
  • Hi @chathuri kaluthanthri - You can create a new Classic project based on an existing Classic project - but you can't do that with Next-gen or Service Desk projects. Then you can Move the issues from the first project to the new project. 
  • Yep - that was it. ;-)
  • Here's a link to some more info/points of view: https://community.atlassian.com/t5/Jira-questions/Why-is-my-custom-field-locked/qaq-p/1000282 I don't know if exactly every problem that would erupt, but most likely it would cause add-ons to not function correctly at a minimum. 
  • Hi @JCaltagirone - Welcome to the Atlassian Community! This is by design now due to GDPR.
  • Hi Dionei - I cannot urge you strongly enough to change it back to Epic. You will encounter so many problems that I can't even begin to describe. My bottom line recommendation - DON'T DO IT!!
  • Hi Sourav - Welcome to the Atlassian Community! You can direct the Approval to go to a certain status, then maybe you can put a transition screen on the transition to that status. Not sure it will fire that screen or not. I populate the Approvers field using Automation based on the value of another field that is capturing…