youngmon/atlassian-qna huggingface dataset:
Issue type "Separators" disappeared from backlog
Asked by bobby:

I had separators in my backlog to divide the backlog into different sections. "Ready", "Needs design" etc. SInce a few weeks they have disappeared from backlog and are no longer visible. When searching I can find them but can't make them visible. Can anyone help?   

Thanks


Answers:
author: Walter Buggenhout
body: Hi [@bobby](/t5/user/viewprofilepage/user-id/5539462) and welcome to the Community!

That's a creative approach you're applying there to create sections in a backlog ? ...

Since you created an issue type for this, it will also be linked to a workflow. If you can still find the issues via search, check what status they are in and make sure this status is mapped to the backlog column of your board (assuming that you're using company managed projects). If that's not the case, update your issue's status or the boards status to column mapping.

If that's not the cause, check your board filter / sub filter / quick filters to make sure they are not filtering out your issue types.

Hope this helps!


Tags: cloud

jira-service-management

jira-service-management-cloud
Sprint start/stop behavior when stories under epics are in different projects
Asked by Dick:

Hi all,  
In my company, management decides which business cases (read: epics) are to be worked on. These epics reside in project A.  

We have multiple teams working on these epics, making stories in their respective projects.

In order to help the teams to find the correct epic, we filter in the epics using the board filter, these are displayed in the epic pane, where you can choose the "create story in epic" shortcut.

The problem:  
In order to start/stop their sprints, the teams need both permissions in their own project **and** project A. The latter is undesired. How can we get around this additional prerequisite?


Answers:
author: Matt Parks
body: What happens if the stories aren't linked to the epics when you try to start the sprint?

On a more general note, what is the concern with users being able to manage sprints in project A (or any project, for that matter)?

As a rule, I am in favor of locking down as little in Jira as possible unless there is a compelling reason (e.g. the Jira project that our Threat and Vulnerability Management team uses is tightly controlled). I can't think of a compelling reason why users should be restricted from managing sprints across any project, so I give any logged-in user the ability to manage sprints on all projects.

Locking things down for the sake of locking things down leads to problems like what you're experiencing now, where you would have to fundamentally change how you use the tool to accommodate a restriction that doesn't need to be in place.

comments: author: Dick
body: Exactly!   
There is no reason ++whatsoever++ to put these restrictions on the Team project sprints in the aforementioned way. Even when I gather their own issues on another board (so without the epic issues of project A, yet still with the epic link fields of the issues referring to the epics in project A), the restrictions on the sprint start apply.

I'm at a loss here.


Tags: data-center

jira-data-center

permission

sprint
Automation rule to link issue type to Epic already linked to a Story
Asked by Emna Elleuch:

If we supposed, i have a Story Linked to an Epic, and then i will add Task, Bugs or Dev/QA Stories and link them to the Story.

how can I add an Automation Rule to link all the items: Task, Bugs and Dev/QA Stories to the same Epic linked to that Story?

I would like to use the Clock Work App and get the time spent for all Epic so I think everything need to be linked to that Epic, and unfortunately sometime the team forget to link do the necessary updates

Thanks in advance for your help!


Answers:
author: John Funk
body: Hi Emna,

When you are linking the issues to the story, I assume that is by the issue linking functionality. So, you could create an automation rule based on an issue linked. And then add a branch for the linked issue. Under the branch Create a variable to identify the parent of the linked issue - something like {{issue.parent}}

Then use the variable to Edit the issue to update the parent field of the Bug, Task, etc.

comments: author: Emna Elleuch
body: Can you please share a screen how we can add this variable ?


Tags: cloud

jira-cloud
Advanced Plan Sorting when Grouped by Goals
Asked by Fahim Ahmed:

Hi,

We are using Goals to map against Projects.

On Advanced Plan view I want to see a view 'Grouped by Goals', however ideally I want to sort these into order (i.e. denoted by the 1a, 1b, 1c, 2a, etc) - at the moment it appears random and not sure how to order numerically - is there a way of doing this?

![Capture.PNG](/t5/image/serverpage/image-id/334249i4EAA9A29EB012138/image-size/large?v=v2&px=999 "Capture.PNG")


Answers:
author: Lisa Forstberg
body: Hi [@Fahim Ahmed](/t5/user/viewprofilepage/user-id/5268205)

Sort order by goals is not yet possible, I found this feature request for it: <https://jira.atlassian.com/browse/JSWCLOUD-26869>

You can filter by goals but that's not helping much I know.

![Screenshot 2024-08-06 at 12.11.12.png](https://community.atlassian.com/t5/image/serverpage/image-id/340221iB21C916245517320/image-dimensions/510x414?v=v2 "Screenshot 2024-08-06 at 12.11.12.png")

comments: author: Vincent Van Dintel
body: This is sorely needed - without it, grouping by goals is not very useful for me. Ideally I want to be able to sort the goals by the goal's target date.


author: Lisa Forstberg
body: vote for it on the link ---\^. ;-)


Tags: cloud

jira-cloud
Adding/Removing stories to an ongoing sprint
Asked by Smitha Joseph:

Can you still keep adding or removing stories to your ongoing sprint? Would that be considered as a scope creep?

Can the team re estimate the story(reduce/increase) of an ongoing sprint once they realize they have estimated it incorrectly?


Answers:
author: Rebekka Heilmann _viadee_
body: Hi [@Smitha Joseph](/t5/user/viewprofilepage/user-id/5524135)

you can do all these changes, for some of them you'll get a warning prompt that you can choose to ignore.

Changes in scope and/or estimation will be reflected in the Sprint Reports.

Regarding the "Scrope creep", it's certainly not ideal to constantly change the scope of a Sprint. If you notice you start pullling Stories out the Backlog every Sprint, you can probably just start with more Stories/Story points to begin with. That's method though, not tool.

comments: author: Smitha Joseph
body: Thank You [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) for answering my question .


Tags: cloud

jira-cloud
Recalculate Sprint Team Capacity?
Asked by Smitha Joseph:

I calculate sprint team capacity as

\[ (count of team members \* 8) - (Sum of the Planned leaves + Holidays)\] // team members - DEV \& QA resources

Should the sprint team capacity be recalculated with unplanned \& sick leaves once the sprint starts?


Answers:
author: Bill Sheboy
body: Hi [@Smitha Joseph](/t5/user/viewprofilepage/user-id/5524135)

In my opinion, "no".

There is always uncertainty related to the work requested, the solution approaches the team selects, any forecasting / sizing of work, emergent business priorities, technical impediments, and certainly, the people-related things:

* availability of people on the team
* shared understanding
* knowledge silos
* team health
* focus
* etc.

During the sprint, the team could identify and communicate to stakeholders when things do not go as expected for the sprint plan and goal.

Perhaps discuss with the team how team-sprint-capacity is being used, its effectiveness to meet that need, and how to learn and experiment to improve when things do not go as planned. The retrospective is an excellent time to do this.

Kind regards,  
Bill

comments: author: Smitha Joseph
body: [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) Thank you. I understand the planned capacity remains the same throughout the sprint. Do you recommend having a buffer for the team capacity to meet these uncertainties.


author: Bill Sheboy
body: Yes, and...

Sometimes scrum teams leave buffer capacity to help with both uncertainty and emergent opportunities. Teams may also have production support responsibilities, and that could generate unplanned work. There are several ways to handle these sources / impacts to work, including using a buffer *and* ensuring there is enough ready-work to take on if the team finds itself with additional capacity during the sprint.

When the team discusses to learn where they regularly have unplanned work or uncertainty (i.e., *known* unknowns), perhaps that could be accounted for in planning as a mitigation. Better still, perhaps the team can identify ways to eliminate such impacts.


Tags: cloud

jira-cloud
Not recieving Email Notifications from Jira
Asked by Kay Kalunga Kabwe:

I have several subscriptions running daily but I haven't received any Emails today.


Answers:
author: said kouzibry
body: Hello Kay,

I assume this is on Cloud, not Server/DC.

Check if those subscriptions have any tickets to notify you. The default behavior for subscriptions is to not send out the email if the filter returns no tickets.

Second point is to check whether the Outgoing mail is enabled in your instance.

Here are some useful links :

* [Outgoing Mail in Jira Cloud](https://confluence.atlassian.com/jirakb/outgoing-mail-in-jira-cloud-1206796735.html)
* [Manage filters](https://support.atlassian.com/jira-software-cloud/docs/manage-filters/)

comments: author: Kay Kalunga Kabwe
body: I have actually set them to send me Email even if no tickets are returned. There are tickets in the filters. Outgoing mail is enabled for the instance


author: John Funk
body: Hi Kay,

So no emails from Atlassian at all? If not, you might want to open a support ticket with them to see if your email address got put on the Suppression list for some reason.

<https://support.atlassian.com/contact/#/>


Tags: cloud

jira-cloud

jira-service-desk-cloud
How can the blue AI underlines in the description of the Jira tickets be disabled?
Asked by Mark Vincze:

Since one of the updates, blue underlines started appearing on some words in the descriptions of our Jira tickets, which provide AI summaries.

How can this feature be disabled?


Answers:
author: Callum Carlile _Automation Consultants_
body: Hi [@Mark Vincze](/t5/user/viewprofilepage/user-id/4870134) ,

There is currently a setting in Confluence to disable this, however this is not yet available in Jira. It sounds like it is being worked on currently though - see answer [here](https://community.atlassian.com/t5/Atlassian-Intelligence-Questions/AI-Definition-feature-Feedback/qaq-p/2738138).

I hope this helps!

comments: author: Mark Vincze
body: Hi [@Callum Carlile _Automation Consultants_](/t5/user/viewprofilepage/user-id/2348878) , thanks for the quick reply!

Indeed, that's what I was looking for, looking forward to having that option rolled out.


Tags: ai

cloud

jira-cloud
Closed & Resolved states in JIRA
Asked by Smitha Joseph:

Should the team be moving the issue in Jira to Resolved state once dev \& QA work is completed, and it should be the PO who accepts the story is done moves it to Closed state? Would the issue move to Resolved or Closed state if I moved the issue to Done state in Kanban board.


Answers:
author: Rilwan Ahmed
body: Hi [@Smitha Joseph](/t5/user/viewprofilepage/user-id/5524135) ,

Each Organization and teams have different flows. You need to contact your scrum master or the Jira admin to know the process followed in your organization or how it is setup in your Jira instance.


author: Matt Parks
body: Moving the issue to the column that you have labeled 'Done' on your Kanban board will transition it to the status that is mapped to that column. If the Resolved or Closed status is mapped to that column it will be moved to that status when you move the issue to that column.

I agree with Rilwan's comment that the decision as who is responsible to move the story to particular statuses is an organizational decision and you should set up your workflow, with conditions/validators as appropriate, accordingly.


Tags: cloud

jira-cloud
I can't access my work anymore
Asked by Andre Stander:

I am using same password but can not access the work that I have been doing . All lost now???


Answers:
author: Marc - Devoteam
body: HI [@Andre Stander](/t5/user/viewprofilepage/user-id/5539297)

Welcome to the community.

Are you the org admin of your instance, or just a member of an instance?

If it's the first and you can't access the instance anymore, you have been removed by another org admin or your instance has been removed due to inactivity (free tier instance, if not used for 2 months).

Atlassian would have contacted you via mail to notify you.

Otherwise contact your Admin and let them check your account.


author: Fabio Racobaldo _Herzum_
body: Hi [@Andre Stander](/t5/user/viewprofilepage/user-id/5539297) and welcome,

try to reach the Atlassian support team through <https://support.atlassian.com/contact/> in order to verify your instance status.

Fabio


Tags: atlassian-accounts

cloud

jira-cloud

not-applicable
Automation - Web Request - How to Handle 404 Errors
Asked by Calvin:

Hi all, I have a web request to a link in an automation, the link sometimes gives 404 errors when its down.

The thing is, this completely errors out the Web-request automation. Is there any way to handle these requests, as I'd rather just add a comment to the ticket about the error as opposed to the automation itself failing and emailing the Automation Owner.


Answers:
author: Jehan Bhathena
body: Hi [@Calvin](/t5/user/viewprofilepage/user-id/4851947) ,

Yes, in order to view the web request's status, you need to check the option "Continue running the rule even if the request response is not successful (i.e. non-200 response)"

You can reference this using the smart value highlighted in the image below:

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/334219i5F31834DAEFEED21/image-size/large?v=v2&px=999 "image.png")

comments: author: Calvin
body: Hi Jehan! Thanks so much for the above!

I think I misunderstood the checkbox. I thought it meant "continue running rule" as in continue the web request over and over until a 200. Not that it meant continue the rule as in the whole entire automation!


author: Calvin
body: Tested now and it works perfect, your a legend, thanks!


Tags: cloud

jira-service-management

jira-service-management-cloud
What could be reasons for Predictability to be > 100%
Asked by Rajmohan Maudshetty:

Appreciate thoughts please on reasons for Predictability to be \> 100%


Answers:
author: Bill Sheboy
body: Hi [@Rajmohan Maudshetty](/t5/user/viewprofilepage/user-id/5539246) -- Welcome to the Atlassian Community!

Where in Jira Cloud are you observing an indicator of sprint predictability \> 100%?

Please post an image of the page view which shows this. That may provide more context for the community to offer suggestions. Thanks!

Kind regards,  
Bill

comments: author: Rajmohan Maudshetty
body: Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) thank you very much for your thoughts. Predictability \> 100% is on our project dashboard of which I cannot post an image here, apologies. My current understanding is that Predictability would be \> 100% if PBI is overestimated. I want to know if this is a reason and also if there could be other reasons.

Kind Regards,

Raj


author: Bill Sheboy
body: From what you describe, there may be an error on your project dashboard display or in the measure / algorithm used to determine your value.

You note "Predictability would be \> 100% if PBI is overestimated". That seems like a potential problem. For example, if people are measured (or rewarded) based on improved *predictability* with your measure, they could just regularly inflate estimates! Or as Eliyahu M. Goldratt stated:
> Tell me how you measure me, and I will tell you how I will behave.

Perhaps try this:

* Identify what problem you are trying to solve by measuring "predictability" in this way. That is, "why do that?"
* Describe what "better" would look like *for that problem*
* Identify how you would know things are "better" through observation
* Identify how you would measure that
* Now you may have a measure more aligned to the problem you are trying to solve, and that could be used to assess progress


author: Rebekka Heilmann _viadee_
body: Hi [@Rajmohan Maudshetty](/t5/user/viewprofilepage/user-id/5539246) and welcome to the Community,

could you give us a little more context to your question?

comments: author: Rajmohan Maudshetty
body: Hi [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) thank you very much.

I am trying to understand the reasons why Sprint predictability for a Scrum team could be \> 100%. Thanks


author: Rebekka Heilmann _viadee_
body: What do you mean by "Sprint predictability" though? You mentioned a Dashboard above. I've not heard of a Gadget with that name. Are you using a Third Party App? What does it predict exactly?


author: Rajmohan Maudshetty
body: Hi [@Rebekka Heilmann _viadee_](/t5/user/viewprofilepage/user-id/5182395) , Greetings.

Sorry I meant to say 'Team Predictability' \> 100% on our project dashboard. I am discussing with the owner of the dashboard to understand how 'Team Predictability' is being determined.

I generally brought-up in this community, as to why Predictability would be \> 100% and what should be the corrective actions.

Kind regards,

Raj


Tags: cloud

jira-cloud
Infodation Test Management system: how to change issue type?
Asked by Dany Bellacen:

Infodation Test Management system:

how to change issue type from "Task" to another issue type


Answers:
author: Marc - Devoteam
body: Hi [@Dany Bellacen](/t5/user/viewprofilepage/user-id/5506261)

Looking at the app and its documentation you wil need to add issue types to your project.

See: <https://itms-documentation.infodation.com/configuration-for-jira-project/>

Otherwise contact the vendor and ask them to help out, as this relates to their product.

comments: author: Dany Bellacen
body: I've done those steps but the created issues are type "Task"

I want to change it to other type "Automation test"

I didn't find how to do that.


author: Marc - Devoteam
body: Hi,

Is the new issue type part of the issue type scheme of the project or projects you are using?

And are you creating the issues within Jira or via the API?


author: Dany Bellacen
body: It is part of the project.

via Jira.


author: Marc - Devoteam
body: Then if you have added the issue types as explained in the documentation of the app, you should be able to choose them on creation.

You can make a Epic, Story, Bug, Task and New issue types you have created for Test.

Can you provide details (screenshots) of your issue?


author: Dany Bellacen
body: this is my problem...

in the beginning, I've chosen issue type "Task" (by mistake)

now I want to change it to another type, but I didn't find a way to do it.


author: Marc - Devoteam
body: Hi [@Dany Bellacen](/t5/user/viewprofilepage/user-id/5506261)

Add a new issue type to the project and bulk change al tasks that represent tests to that new issue type.

Would that solve the issue, I don't know as, I don't know the app.

I would give this a try in the sandbox, or create a dummy project with the exact same setup, as you currently have, and try it there.

Or reach out to the vendor if this is possible or not. I can't find anything in their documentation.


author: Dany Bellacen
body: I have already tried it without success.

update me if you find something as soon you will try it.

Thanks,


author: Marc - Devoteam
body: Hi [@Dany Bellacen](/t5/user/viewprofilepage/user-id/5506261)

I don't use this app, just looking at the functionality and the doc's these were my suggestions.

My advice is to to reach out to the the app developer support and see if they are cable to help on this topic


author: Dany Bellacen
body: Ok, Thanks.


Tags: addon-itms

atlassian-marketplace

cloud

jira-cloud
Closed and resolved status in JIRA
Asked by Smitha Joseph:

What is the major difference between closed and resolved status of issues in JIRA? Does the team move the story to Resolve state and PO on accepting the story moves it to Closed state? What state is the issue moved to when moved to Done state in Kanban board?


Answers:
author: Joe Pitt
body: Depends on your system.

Most people build their workflows so the when moving to the Closed status the resolution field is set with the desired value and no additional work is needed. In that scenario there isn't a difference. To Jira when the resolution is set it gets a strikethrough in the issue ID when referenced in a link.

I've seen some systems where the resolution field is set when the developer believes the bug is fixed and the workflow continues for steps for testing or deployment. In that workflow closed would be at the end of testing or deployment.

On a board 'Done' is they far right position AND the resolution is set.


Tags: cloud

jira-cloud
Can a team management project control the permissions of a single issue?
Asked by Easy Healthcare:

Can a team management project control the permissions of a single issue?


Answers:
author: Prachi Bolar
body: Hello [@Easy Healthcare](/t5/user/viewprofilepage/user-id/5450051)

Thank you for contacting Atlassian.

I understand you are looking for a feature to restrict single issue in a Team managed project. ( TMP)

Presently in TMP its possible to restrict an entire issue type and not a single issue .

We dont have the feature yet to restrict a single issue in TMP like the one in company managed project with the help of issue security scheme ( <https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-security-schemes/>)

A feature request has been raised for the same : <https://jira.atlassian.com/browse/JSWCLOUD-18843>

SNippet from TMP project on how you can restrict an entire issue type from users

**![Screenshot 2024-07-09 at 12.06.31?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/334199i4B4B5145320A5BA4/image-size/large?v=v2&px=999 "Screenshot 2024-07-09 at 12.06.31?PM.png")**

comments: author: Trudy Claspill
body: [@Prachi Bolar](/t5/user/viewprofilepage/user-id/5217155)

Your answer appears to be partially incorrect. You **can**restrict an individual issue in a Team Managed project.

If you click on the padlock icon on an individual issue you can specify the Roles that can see that single issue.

![Screenshot 2024-07-09 at 7.47.55?AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/334339i3E9FC4CE2733E1C8/image-size/large?v=v2&px=999 "Screenshot 2024-07-09 at 7.47.55?AM.png")


author: Easy Healthcare
body: Don't team-managed projects have transaction security levels? {#toc-hId--353253367}
-----------------------------------------------------------------------------------

comments: author: John Funk
body: No


author: Trudy Claspill
body: Hello [@Easy Healthcare](/t5/user/viewprofilepage/user-id/5450051)

Have you looked at the Issue Security feature for Team Managed projects?

<https://community.atlassian.com/t5/Jira-articles/Announcement-Control-access-to-your-issues-on-next-gen-using/ba-p/1430115>

<https://support.atlassian.com/jira-software-cloud/docs/set-up-issue-types-in-team-managed-projects/#Setupissuetypesinnextgenprojects-restrictIssueTypesRestrictaccesstoanissuetypeinyourteam-managedsoftwareproject>

If that doesn't meet your needs can you provide more specific details about what you want to control?

comments: author: Trudy Claspill
body: [@Easy Healthcare](/t5/user/viewprofilepage/user-id/5450051)

Please explain with an example what you mean by transaction security levels.


Tags: cloud

jira-cloud