Comments
-
So what is really different in the new view? I’m second guessing things here. For example here is what I see on one project…
-
Are you asking if you can change the project template once created? If so no. You have to create a new project.
-
That doesn’t appear to be an option to opt in. Rather it is just an FYI that things have changed. to be honest I’m not sure how different this is until I play with it. Can you still add fields to the cards?
-
It is there for me. Please share what you see. I assume you are indeed using a CMP project.
-
Hi Jonathan welcome to the Community. To be clear you don’t “link boards” in Jira. You can link issues between projects. Boards are visual representations of a filter query. If you are asking how to create an issue in a JSW project that relates to a JSM issue then consider using “Create linked issue” in your JSM project to…
-
I suspect you are wanting something like this… "Epic Link" != “xxxx” and "Epic Link" is not empty you need to find the epic link associated with the epic of interest here and replace “xxxx”. The is not empty is to ensure you exclude stories that don’t belong to any epic.
-
Если вы спрашиваете, как создать повторяющуюся задачу dally, я бы порекомендовал вам взглянуть на автоматизацию. Триггер - по расписанию ежедневно Условия - все, что соответствует вашим потребностям Действие - создать проблему
-
That capability doesn’t exist within Jira. You would need to consider using an external user directory solution like Active Directory.
-
it is new to me. I also checked the release notes and couldn't find anything. I have posted something in the slack channel with others to see if anyone else has any ideas.
-
First, understand boards are driven by a board filter. So if you don't want certain issues to show on a given board then you need to figure out how to exclude those issues. So the question is, how do you differentiate your internal issues? Is it issue type or label or component or something else?
-
First to be clear I assume what you're wanting to count here is the number of times an issue is in affect re-opened since resolution date basically is set when issue is marked done. you can use Automation to increment the field. trigger - issue transitioned Condition - status = done Action - use math expressions to add +1…
-
odd... scratching my head. might be a question for Atlassian.
-
Interesting it appears in the new view they've gone to a single line with an arrow that scrolls to the right is that correct?
-
let's here it for Marie Curie!
-
While a customer can use email to create and comment on requests they would have to login to view requests in the portal. Any link provided with in the email will resolve to the portal. Without logging in there would be no way of knowing what to display to a user.
-
Here is a reference that might be of interest - what-are-team-managed-and-company-managed-projects
-
It won’t impact existing projects particularly your team managed projects. The point with CMP projects is that they can share schemes, issue types etc. However, they don’t have to. When you create the first project it will be all alone and not impacting any other project. However, let’s assume you create a second CMP…
-
The text in the portal is not as yet configurable.
-
Yes I would concur that if you “remove” an issue from the sprint before completing the sprint it should show under issues removed. How are you removing the issue. I just ran a quick test and simply updated the sprint field to remove the Sprint. I then completed the sprint and the behavior was as I expected. That is,…
-
I suggest you use the Create linked issue. I use Automation that triggers when a JSM issue transitions to Development status and if certain conditions are met then I create a linked issue in the appropriate software project. I have another automation rules that keeps the JSM ticket in sync with the JSW project ticket.
-
Can you share a screenshot of what you are seeing in this new view?
-
Ok. For the project associated with these issues please go to the following location and give me the screenshot. Project settings > Automation I want to see the list of rules for that project and please indicate which rule is in question here. Similar to below.
-
Sprint report will always, and correctly so, show the deviation from your committed plan. If you remove issues or add issues to a sprint after it has started it will show up in your sprint report. The reason the issues are showing in the backlog is because you remove them from the sprint at which time they will be sent…
-
You could create an automation rule and custom field and increment that field every time an issue moves to a done status category.
-
You might consider an addon like exalate-jira-issue-sync-more or check out other similar marketplace app.
-
Currently JSM does not support customer profiles. Profiles are only provided to licensed users.
-
There are a number of ways of implementing this however based on what you have stated here I might do the following. create projects: * Product Requirements (business template) * Product Development (software template) product requirements bullet points: * issuetype - Feature Request * workflow - New > Assessment > Done *…
-
Hi Danielle, Have you considered simply requesting that the customer close the issue from the portal? You can expose the transition to close the issue on the portal such that the customer can resolve issues themselves. If you work entirely in the email world then you could indeed send an email requesting that they respond…
-
It is because you are on the Free plan which limits the number of emails that are sent out to I believe 100 per day.
-
On Aug 10 you replied to Melo with an image of the audit log but it was only for the config change. The point is that The audit log is in that very place where you took that image. project settings > automation > audit log find the entry that is associated with the create issue event. It may show success or failure. Click…