youngmon/atlassian-qna huggingface dataset:
Jira Work Management: Add Child Issues to back into Document Approval Template
Asked by Roxsanne:

Jira Work Management: Add Child Issues back into Document Approval Template.  

**Is this possible?**


Answers:
author: Ste Wright
body: Hi [@Roxsanne](/t5/user/viewprofilepage/user-id/5166434)

You can't edit the template itself, but once a Project is created, you could add Sub-tasks (or Epics, as a parent) if needed.

The instructions differ depending on if this is Team-managed or Company-managed...

---

**Team-managed:**

You'll need to be a Project Admin, and then...

1. Select the Project Settings tab (furthest to the right)
2. Select Issue Types from the left-hand menu
3. Choose Epic or Sub-task

---

**Company-managed:**

You'll need to be a Product Admin, and then...

1. Select the Project Settings tab (furthest to the right)
2. Select Issue Types from the left-hand menu
3. Select Actions (top-right corner) \> Edit Issue Types
4. Check which Projects use this Scheme (just under the name it states "Shared by N Projects") - and ensure all listed Projects require this change
5. Drag required issue types from the right-hand column into the left-hand one
6. Press Save

A few notes on this one...

* If some Projects using the issue type scheme do need Epic/Sub-task, you might be better to create a new Issue Type Scheme, modify it as needed, and then apply it to each relevant Project
* For Epics, you might need to add/modify the screen, to add fields like Epic Name, Epic Link, etc. This will soon change though, see [this help page](https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/).

---

Let us know if this helps, or if you need any further instructions :)

Ste

comments: author: Roxsanne
body: Thanks!


author: Ste Wright
body: No worries!

If this helps to resolve your query, could you accept it? That helps other users know this answer is a solution :)

Ste
Automation: Link to child issue of {{createdIssue.key}}
Asked by Nguy?n Th?nh Long:

I am having a quite specific problem that I am not able to look for solutions myself or from googling.  

I set up a workflow where user submit ticket through a service project and that in turn will trigger an Epic to be created in a different software project. The creation of this Epic will in turn trigger creation of a child issue.  
For users to understand the progress of their ticket I would like to set a comment that link to the newly created child issue. I was able to comment link to the epic in the original service project ticket.  
Hope I am clear here.

Thanks


Answers:
author: Charlie Misonne
body: So you have this flow: service project ticket -\> epic -\> child ticket

You can add a link to the epic in the project ticket because the project tickets triggers your automation rule to create the epic. So the project ticket is accessible via the automarion rules.  
That's how I assume you did it.

And the creation of the child item is done by another automation rule?

How I would do this:

Rule 1: creates the epic when service project ticket is created + **links** the service ticket and epic together with an issue link using the **link issues**action

Rule 2: creates the child issue when the epic is created. + with a **For each - Branch rule / related issues** you specify the link type you used in rule 1 and create a comment on the original service ticket with the URL to the createdIssue.

I hope this gives you some insights.

comments: author: Nguy?n Th?nh Long
body: Hi Charlie,

Thanks for the suggestion. I actually had this idea in mind since the trickiest part of this problem is there another layer of new vs trigger issues relationship. However, I was not able to reproduce the solution in jira automation. I am not from technical background (as you can refer from my question) so would I really appreciate if you can help me with how can I set this up in automation.


author: Charlie Misonne
body: Hi Nguy?n,

Can you tell me where you are stuck please. I did not fully understand your last reply, I'm sorry.


Tags: cloud

jira-work-management-cloud
As an admin, why I get to a message 'need an approval from admin' when I added a new user?
Asked by Nam Stevenson:

Not sure why I get to see the message as I'm an admin. I did check with the new user I just added and she got in successfully. Is the message legit? Or just a reminder? Thanks!


Answers:
author: Mohanraj Thangamuthu
body: Hello. Good day. Kindly check the user access setting. Thanks

![Screenshot 2023-08-07 at 12.10.50 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/273494i1970C18EB7F425A2/image-size/large?v=v2&px=999 "Screenshot 2023-08-07 at 12.10.50 PM.png")![Screenshot 2023-08-07 at 12.10.59 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/273495i56D16DA8FBCBAA72/image-size/large?v=v2&px=999 "Screenshot 2023-08-07 at 12.10.59 PM.png")


author: Brant Schroeder
body: [@Nam Stevenson](/t5/user/viewprofilepage/user-id/5277939) Welcome to the Atlassian community

As a Jira admin you will be able to administer users on your product but not for the whole organization. Adding a user can impact licensing and the organization admin has it setup that he needs to approve these users before the can be added. <https://support.atlassian.com/organization-administration/docs/what-is-an-atlassian-organization/>

comments: author: Nam Stevenson
body: Thank you Brant, that makes sense. FYI, I am not an organisation-admin. Another admin granted me an admin access. After adding me as an admin, both of us got the alerts when we added more users. He mentioned that it never happened to him before when he added more users. Bad timing with the limited licensing issue?


Tags: cloud

jira-work-management-cloud
Jira queries required to pull Epic ticket
Asked by Rajakumaran Balashanmugam:

Trying the pull the Jira epic in issues search below format but getting an error "Epic Link" = ("O000000looooo")

please help


Answers:
author: Ste Wright
body: Hi [@Rajakumaran Balashanmugam](/t5/user/viewprofilepage/user-id/5232283)

Are you looking to locate all Epics? If so, you could use...

```
issuetype = Epic
```

If it's one specific Epic, you could use key - such as...

```
key = ABC-123
```

And if you're looking for all issues within an Epic, for Company-managed Projects it would be...

```
"Epic Link" = ABC-123
```

And for Team-managed...

```
parentEpic =?ABC-123
```

---

If none of these are what you're looking for, give us more details about what you need so we can help further!

Ste

comments: author: Rajakumaran Balashanmugam
body: Hi Stephen ,  
thank you for responding to my query   
I am trying to pull all the issues in one Epic   
I tried with Epic Link but i am getting that perator '=' does not support the list value '("XXX-oooo")' for field 'Epic Link'.


author: Ste Wright
body: Hi [@Rajakumaran Balashanmugam](/t5/user/viewprofilepage/user-id/5232283)

What is '("XXX-oooo")' representing in this instance?

You should be utilising a single Issue Key, eg. ABC-123.

If you want to include multiple Epic keys, you'll need to use:

```
"Epic Link" in (ABC-123, ABC-456)
```

Ste


author: Rajakumaran Balashanmugam
body: It is Epic Name


author: Ste Wright
body: You need to use the Epic's **Issue Key**- this is the unique identifier based on the Project Key and a numeric value - for example...

* ABC-123

Ste


author: Rajakumaran Balashanmugam
body: Stephen, Were do i find the Key link in my Epic


author: Rajakumaran Balashanmugam
body: Got it and resolved and thank you


author: Ste Wright
body: Excellent, great to see you found it!

If this answer helped to resolve your query - could you accept it, so others know it can help them too? :)

Ste


Tags: cloud
This site is already taken at Jira Work
Asked by Eldon Clayton:

I can't be able to create our account and site to start with Jira Work Managemment.  

I already tryied a lot of variations, with no success.  
Can you help me?  

![Screenshot 2023-08-02 110327.png](https://community.atlassian.com/t5/image/serverpage/image-id/272747i2B49A7A47BD45712/image-size/large?v=v2&px=999 "Screenshot 2023-08-02 110327.png")


Answers:
author: Kian Stack Mumo Systems
body: Someone else just posted a similar question about this. I was able to get a site name working just a few minutes ago, so perhaps it was a temporary issue? I'd recommend trying a completely unique string to see if you can get that to work and then try to find a name that works for your organization.

Thanks,

Kian

comments: author: Nic Brough -Adaptavist-
body: You can change the site name later, if you set up a temporary unique string for your new site.
Can you see all your different projects with their tasks and sub-tasks together in one list view?
Asked by Sharon:

I'd like to be able to see a view of all my projects, with the related tasks and sub-tasks on one page, so a bit like the current list view but showing all projects.


Answers:
author: William Ramaki
body: You can maybe use the Dashboard, where you can add all your projects and the subtasks. It works for me.

comments: author: Sharon
body: Thanks, I'll give it a try!


author: Veronika Bridgman
body: Thanks William - how exactly did this work for you in dashboards? I'm trying to do exactly what this thread is talking about - view all tasks across multiple projects. And be able to see it by assignee... I can add a widget where I see this for me, but not for others.


author: Hannes Obweger - JXL for Jira
body: Hi [@Sharon](/t5/user/viewprofilepage/user-id/5282949)

Jira's built-in Advanced Issue Search (a.k.a. *View all issues* ), under *https://\<your-jira-site\>/issues* allows searching for and listing issues across projects. While you can use [JQL](https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-14) to sort and group your issues, it won't quite give you the experience you are used to in the list view.

Alternatively, if you are open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2438044).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you'd do in e.g. Excel or Google Sheets. In a sense, it has a view things in common with JWM's list view, however JXL comes with a range of advanced features - plus, it can be used as a cross-project view on your issues!

This is how this could look in action:

![project-issue-hierarchy.gif](https://community.atlassian.com/t5/image/serverpage/image-id/272739i2044741B5B1FB057/image-size/large?v=v2&px=999 "project-issue-hierarchy.gif")

Another advantage is that JXL works with projects of any type, not just JWM projects.

Any questions just let me know,

Best,

Hannes


Tags: cloud
AUTOMATION: Linking Epic to the issue
Asked by Jasmine Pennala:

Hello!  

I have 2 problems that I am hoping someone can help with.   

**1)** We created a manual trigger to create a new issue. It copies all the fields correctly and links any related issue, but the only problem we keep hitting is that it does not link the Epic that it was created from.  
Attached are pictures of what we have on the automation. Is there a way to fix it so the manually triggered issue links to the epic? The epic does not link the issue that was created either.  

As a note, I did try each entry option under "Epic Link" on the automation and it did not change anything.   

<br />

<br />

**2)** When an issue is created from an Epic, the Epic does not link next to the issue key (picture is attached as the last one)  

<br />

Screenshots for the first Question:

![Concurrent Automation.png](https://community.atlassian.com/t5/image/serverpage/image-id/272294iD349D58BAA9DDB90/image-size/large?v=v2&px=999 "Concurrent Automation.png")![Concurrent.png](https://community.atlassian.com/t5/image/serverpage/image-id/272295i00DA2A29F13B3923/image-size/large?v=v2&px=999 "Concurrent.png")  

<br />

Screenshot for the second question![Screenshot 2023-07-31 160825.png](https://community.atlassian.com/t5/image/serverpage/image-id/272296i52C631BC29F02CE0/image-size/large?v=v2&px=999 "Screenshot 2023-07-31 160825.png")


Answers:
author: John Funk
body: Hi Jasmine,

Use {{triggerIssue.key}} for the value in the Epic Link field.


author: Trudy Claspill
body: Hello [@Jasmine Pennala](/t5/user/viewprofilepage/user-id/5234396)

Question 1:

Are you using this for issues in a Team Managed project or a Company Managed project?

Have you tried selecting "Copy from trigger issue" instead of "Copy from issue"?

I tried both in a Team Managed project and a Company Managed project, and "Copy from trigger issue" successfully made the new issue a child of the same Epic as the trigger issue.

Question 2:

Exactly what steps are you executing to "create an issue from an Epic"?

Are you using the default issue hierarchy of Epic \> standard issue types \> subtasks? Or has the issue hierarchy been extended above Epics in your instance?
Unable to mention or tag someone in Jira Comments.
Asked by Larrubis Michael:

Hey guys,  

Would like to raise this issue since I was unable to tag or mention in the comments.  
I would suggest to remove the placeholder \`**Type @ to mention or notify someone** \` for those users that cannot tag or mention in the comments.  

It would be great the JIRA dev/staff be able to address this.


Answers:
author: Prachi Bolar
body: Hi [@Larrubis Michael](/t5/user/viewprofilepage/user-id/5281460) ,

Welcome to Atlassian Community :)

I understand that you are unable to @mention users in the comment section of your project.

You need to have **Browse users and groups** in global permission.  
To access and edit your site's Global Permissions do the following:

1. Choose \> **System**.

2. Click**Global Permissions**.

3. Make sure your user is included in the Users / Groups that have the **Browse users and groups**permission.

I hope this information helps.

Thank you,

Prachi


author: Nic Brough -Adaptavist-
body: Welcome to the Atlassian Community!

Does your account have the global permission for "browse users"?


Tags: cloud
Advanced Roadmaps scrum team shows weekly capacity in hours per week, should be story points
Asked by Thayne Munson:

My team in Advanced Roadmaps was originally set up as Kanban but I want to switch it to Scrum. I changed the associated issue source to a scrum board with a team type of scrum. I confirmed in my scrum board configuration that the estimation statistic is set to story points. When I try to update the story points iteration capacity it still reads as capacity (weekly hours). Am i missing a change somewhere? Thanks.


Answers:
author: Thayne Munson
body: It appears there was some time delay when I changed the team to scrum from kanban. It is correctly showing capacity in story points. Thanks.

comments: author: Dave
body: I'm glad you were able to resolve this situation [@Thayne Munson](/t5/user/viewprofilepage/user-id/4031047) - did this require a reload of the plan to fix things? Or was it just a time delay with the page loaded.

Regards,

Dave


author: Thayne Munson
body: I believe it was just a delay. Thanks for responding.


Tags: advanced-roadmaps
Issue number not assigned when saving Advanced Roadmap in Jira
Asked by Deon Singh:

My RoadMap is called "Resource Plan".

After creating an epic, capturing start and end dates and adding an estimate, i go to "Review Changes". I click on "Save selected changes in Jira" to save my changes.

My changes are saved, however the issue number is not populated and saved. It just shows - RS instead of RS-79 and RS-80, etc. for the different issues I captured.

I logged off, waited a while and then re-tried and it seemed to have then worked.

Wanted to know why this happened. It has only occurred once so far.

Thanks,

Deon


Answers:
author: Curt Holley
body: Hi [@Deon Singh](/t5/user/viewprofilepage/user-id/4378677) Can't say I've ever experienced this....and if it is just a one-off I wouldn't worry too much about it.

Could be network and/or caching oddity. Could be the browser. Mystery of Cloud....

But!!! If you notice this happening regularly, raise it with Atlassian support.

Fingers crossed though, that you never encounter it again.


Tags: advanced-roadmaps

cloud
Remaining estimates spread evenly across start date/end date in Adv Roadmaps?
Asked by Jennifer Mancke:

We are working to use Advanced Roadmaps for our teams capacity planning, but we have monthly allocated support hours spread across an annual (or multi-month) term that we have set up as projects in Jira. The way I have seen Adv Roadmaps calculate available capacity is use up the teams capacity for the project ending soonest and pushing out the remaining estimate on all projects that end after, basically appearing that we have enough capacity until we look a year or so out at the latest ending project. I was curious if anyone has found a way to have advanced roadmaps spread out the estimate evenly across the length of the project so we can understand what we need to delivery on on monthly support commitments. TIA!


Answers:
author: Walter Buggenhout
body: Hi [@Jennifer Mancke](/t5/user/viewprofilepage/user-id/4075233),

Advanced roadmaps (and roadmaps in general) is built around the principles of the iron triangle of planning, where you have a certain scope, one or more teams to deliver and your target dates over time.

Support work is not well suited to be managed through a roadmap, as it is unplanned work by nature. Incidents are unpredictable as to when they happen, they are usually solved rather than estimated and - as such - virtually unplannable.

And still, many organisations and teams are working in a hybrid mode, partially doing project work and partially delivering support. And that is often an interesting approach, though often the support workload puts a heavy strain on delivering new value.

It may be a good idea - if you don't do this already - to look at your team's capacity and divide it across project and support work. Remove the support work from your average team capacity. If - a totally random example - your team spends on average 40% of its time on support and 60% on projects, reduce your team capacity by 40% in the plan and only pull your project work in there - not the support.

Due to the unpredictable nature of support, this will obviously vary over time. But the better your high level metrics on this distribution of work, the more reliable your capacity / forecasting will become.

I know this is not a technical answer about the tools, but I still hope it helps you forward in your approach.

comments: author: Jennifer Mancke
body: Thanks Walter. Yeah, we have already accommodated for the split between project and support work.


Tags: advanced-roadmaps

capacity

cloud

plan
is it possible to Automatically change team base on the assigner?
Asked by janendra ranasinghe:

Hi

Two team are working on one board issue. Is it possible to Automatically change team field in the issue base on the assigner?

Scenario:

eg :- 2 teams - Team A (developer), Team B (tester)

Developer (team A) develop the system and assign to the Team B member. It is not change team field in issue automatically. It need to done manually.  
is there way to change this automatically?


Answers:
author: Dave
body: Hi [@janendra ranasinghe](/t5/user/viewprofilepage/user-id/4375627),

Unfortunately this is not possible using just Advanced Roadmaps however it might be possible to achieve this using the automation capabilities included along with Advanced Roadmaps in Jira Premium on Cloud.

When we were developing Advanced Roadmaps (back when it was known as Portfolio 3.0 on Server) we made the decision to not have "magic" behaviour relating to teams and sprints. For example we did consider restricting sprint assignment to the sprints associated with the team or automatically updating the team based on sprint assignment. We also considered doing something similar with teams and assignees. However the reason we opted against this was because it was not possible for us to enforce this within the issue details screen in Jira (and specifically with the case of assignee team there were potential edge cases like the assignee belonging to multiple teams).

Regards,

Dave


Tags: advanced-roadmaps
Auto-schedule issues linked across multiple projects
Asked by Brian Charniga:

Hi,

I have a project that i'm trying to use auto-schedule for. It works fine except for one Story that it skips over for some reason without warnings. This particular Story happens to have a Linked dependency that is blocking it which is assigned to a Sprint that is in a different project - could that be causing the blocked issue to be skipped? There are no warnings, which is odd. Does auto-schedule not work with Linked Issues that are in a different project's sprint? Note - I have included each project's board in my issue sources, so at least the sprints are recognized as part of the plan.


Answers:
author: Dave
body: Hi [@Brian Charniga](/t5/user/viewprofilepage/user-id/4350474),

Can you confirm what you mean by "skips over" - does this mean that the issue is completely ignored and no changes are suggested?

Usually when an issue has no suggestions made it is because it has the optimum values assigned or it has no estimate (issues without an estimate are generally ignored by the auto-scheduling).

With respect to the linked dependency from another project... if that dependency is itself included within the plan then the scheduler will take it into account (in so far as it won't schedule the dependent issue before the issue it depends on). This also relies on the link relationship being included as a dependency in the global configuration for Advanced Roadmaps (by default only the blocks / is blocked by is considered a dependency).

It doesn't matter if the issues are in different sprints / projects / boards - all that matters is that they are both present in the plan and the scheduler can work out start / end dates for them (usually derived by the estimate and assigned team capacity).

Regards,

Dave

comments: author: Brian Charniga
body: Thank you [@Dave](/t5/user/viewprofilepage/user-id/1183605) for clarifying the expected behavior. I took a closer look after getting some sleep and realized this was all due to user error... I totally missed that I forgot to put an estimate on the issue that was blocked, so I fixed that and now everything is working as expected. I'm working on a proof-of-concept using Advanced Roadmaps, and am very happy with the capabilities so far. Can't wait to see what's coming down the road! Thank you!


author: Dave
body: No worries [@Brian Charniga](/t5/user/viewprofilepage/user-id/4350474) - glad I was able to help!


Tags: advanced-roadmaps

cloud