Comments
-
Hi @Graham Harbour have you checked whether the Link Migration tool can help in this scenario? It's build for Server to Cloud migration but maybe it can be used for C2C as well? Update product links after the migration | Atlassian Support
-
Hi @Ceni Krasniqi and welcome to the Community, when using the Jira API, you can put the information directly into the respective Jira fields. Using the description for structured information and then trying to parse out a single value is bad practice. The email-Adress should be added as customer and then used as reporter…
-
Hi @Tushar Rajvanshi per default Jira doesn't give you Time in Status reports apart from the dots on the cards. Check out this article for reference and one alternative: Time in Status in Jira: What is it and how to trac... - Atlassian Community There are multiple Marketplace Apps that can generate reports like the one you…
-
Hi @Joyce Guo and welcome to the Community, are you the Jira Admin? There is a feature called "Notification Helper" in the Administration where you can check notifications for a specific user on a specific issue. Can you check whether you *should* receive notifications? Maybe something has changed. I guess you haven't…
-
As you are in a team managed project, you cannot change the Board's filter. Not in Team managed projects, no.
-
Hi @Santhosh Raj can you post a screenshot of your whole workflow? If I understand correctly, you allow transitioning from all status into all except for the approval part. The system behaviour is correct in that the pending approval doesn't stop other configured transitions from being executed. There are actually several…
-
You can filter for Epics with issuetype = Epic or get all children of a specific Epic with Epic Link = Epic-123. You can reference filters or simply create a new JQL in the Jira macro for Confluence. However, you cannot reference a filter result to search a specific field. Filters can be used in JQL but only in a way that…
-
Hi @reallt and welcome to the community! the order of issues is determined by the Board's filter. Per default that's order by Rank. As you are in a team managed project, you cannot change the Board's filter. Quick Filters cannot change the order of issues in either project type.
-
Hi @Vansh Jain have you tried creating a variable with the value of {{issue.key}} and referencing that? Just a guess - I actually never noticed {{issue.key}} is transformed as a link. It might be that the view/portal is recognizing the pattern and will automatically interpret it as issue link rather than it being formatted…
-
Hi @Florin-Mihai Mot and welcome to the community, I guess the Program Increment Field is a custom field? You can simply search for values within that. Links can be searched per "issueLinkType". The following JQL will give you any issue that has an Issue Link with the Type "is blocked by" or "blocks", is of the issuetype…
-
Hi @john_williams and welcome to the Community, there is no "progress bar" macro per default. You would need Marketplace Apps for that. One would be: Content Formatting Macros for Confluence | Atlassian Marketplace Can you confirm that you have any formatting/macro App installed on your Site? If so, best to contact the App…
-
Hi @David López I would simply create a second rule for Project C. That rule needs to be allowed to be triggered by other rule (in Rule Details). Trigger: Issue created Condition: Project C The rest should be the same as the first rule I guess? Just keep the Automation rule execution limit in mind.
-
Ich freue mich auf euch und den Austausch! Ganz wichtig: Der Vortrag kommt nicht von uns als Atlassian Partner, sondern in der Rolle als "ganz normale" Nutzer und bringt auch Mehrwert für alle, die schon migriert sind oder (noch) keine Migration planen :)
-
Hi @Ste404 check out the API documentation: The Jira Cloud platform REST API (atlassian.com) Interestingly enough, Status doesn't seem to be part of the return value. You could simply try out the WebRequest in the Automation action though. Is there a reason why you are using a WebRequest? You could use "Lookup Issues" to…
-
Hi @Kerstin Thiel and welcome to the Community! I know you said the filter hasn't changed, but can you just make sure it is ordered "by Rank"? Usually this is the only thing that enables/disables sorting. The workflow should have nothing to do with it as I assume you have one status per column?
-
The If-Conditions look wrong. I think it should be {{lookupissues.size}} > 0 Issuetype = Epic -> this will check the trigger Issue's Issue type. Is that what you want? Apart from that simply try it out. I am not too sure what you want to achieve from a business point of view so can't really advise any further.
-
You can use the variable action but you could also simply access the smartvalue straight from the if else. Quick example below. Lookupissues will give you a list of issues. .First will access the first issue in the list. More operations available here: Jira smart values - lists | Cloud automation Cloud | Atlassian Support
-
Hi @Darren Zuiderweg and welcome to the community! Can you specify where you are searching? Are you using the issue search or the "general" search bar (See below) The search bar does a JQL search that looks like this: text ~ "searchstring*". The "text" parameter searches fields like summary, description and comments. Are…
-
No. You cannot share Boards between sites. You can share issues publicly (which is probably nothing you'd want) or use Issue syncing Apps like @Matthias Gaiser _K15t_ suggested. There are multiple Marketplace Apps available.
-
Hi @Aishwariya Rajendran and welcome to the Community, no - Blog posts still only have a "creator" but not an owner. The "Owner" has been introduced to have clear responsibilities for content as Wikis tend to be outdated quickly. Blogs are usually something that is valid at that point in time but don't require regular…
-
Hi @Sanjay Dangi and welcome to the Community! Can you post the part of the rule where you try to populate the field?
-
Hi @aryder Requests can be shared between customers from one Organization per default or if the customer is choosing to do so: Requests automatically shared with organization | Jira | Atlassian Documentation So theoretically, if all your internal customers would be sorted into one Organization in JSM, requests can be…
-
Hi @Divya Sukumaran and welcome to the community! Usually Site Admins will get an Email saying that the subscription has been canceled. Under admin.atlassian.com go to "Billing" and check if the product is still there. It should give you the next billing date, which should be empty. When you click on "Manage" you'll get…
-
Hi @Viresh Kumar the result of the Lookup Issues Action are automatically accessible via the smart value {{lookupissues}} Check out this documentation for more details: Jira smart values - issues | Cloud automation Cloud | Atlassian Support (search for "lookupissues")
-
Hi @Arif K Licensing works per Site. So even if you have multiple Jira Sites in your Organization and User1 is working in all sites, he would be seperately licensed and paid for. One Org has even less to do with another Org, therefore an increase in license count when adding users - regardless of their Org or other Jira…
-
Hi @Nicolas Andika for a backup of the whole site follow this: Export data from Jira Cloud | Atlassian Support Single projects can be now exported/imported with the Cloud migration tool: Cloud-to-cloud migration | Atlassian Support You find it under admin.atlassian.com > Settings > Data Management You can export/import all…
-
Thanks for the Update :)
-
In that case @Dave Rosenlund _Trundl_ posted great Ressources to get started. Keywords to look out for: Transition, Custom Field, Screen, Validator
-
Default = Plain = Jira with no Marketplace Apps installed It is simply different views. The Backlog is part of a Board, which is highly configurable. That includes how times are estimated and also what you see in the detail view, cards etc. The Subtask-List in the "normal" issue view has nothing to do with Boards. It is…
-
Hi @Leyla Lola that's no problem. You need to create a screen first where you add a field for the question. You could either add a "date of birth" date field or you can simply add a number field and validate it in the Workflow. You then create the transition and add the screen and the validator to it. With what step…